updated

git-svn-id: http://svn.code.sf.net/p/docutils/code/trunk@1425 929543f6-e4f2-0310-98a6-ba3bd3dd1d04

1 files changed, 11 insertions, 0 deletions

diff --git a/docutils/docs/dev/todo.txt b/docutils/docs/dev/todo.txt
index c18a81aaa..b1e4f2668 100644
--- a/docutils/docs/dev/todo.txt
+++ b/docutils/docs/dev/todo.txt
@@ -937,6 +937,10 @@ when used in a document.
   - _`misc.settings`: Set any Docutils runtime setting from within a
     document?
 
+  - _`misc.charents`: Equivalent to::
+
+        .. include:: {includepath}/charents.txt
+
   - Docutils already has the ability to say "use this content for
     Writer X" (via the "raw" directive), but it doesn't have the
     ability to say "use this content for any Writer other than X".  It
@@ -1734,6 +1738,13 @@ Instructions for CVS access can be found at
 http://sourceforge.net/cvs/?group_id=38414.  Anyone can access the CVS
 repository anonymously.  Only project developers can make changes.
 
+Unless you really *really* know what you're doing, please limit your
+CVS commands to ``cvs checkout``, ``cvs commit/checkin``, and ``cvs
+add``.  Do **NOT** use ``cvs import`` unless you're absolutely sure
+you know what you're doing.  Even then, grab a copy of the `nightly
+CVS tarball <http://cvs.sf.net/cvstarballs/docutils-cvsroot.tar.gz>`_,
+set it up on your own machine, and experiment *there* first.
+
 The `main source tree`_ ("docutils" CVS module) should always be kept
 in a stable state (usable and as problem-free as possible).  The
 Docutils project shall follow the `Python Check-in Policies`_ (as