Import cvs-1.11.22 onto vendor branch.

1 files changed, 0 insertions, 31 deletions

diff --git a/contrib/cvs/DEVEL-CVS b/contrib/cvs/DEVEL-CVS
index 464003c..3344bd1 100644
--- a/contrib/cvs/DEVEL-CVS
+++ b/contrib/cvs/DEVEL-CVS
@@ -4,37 +4,6 @@ This file, DEVEL-CVS, contains the policies by which the CVS
 development group operates.  Also see the HACKING file.
 
 ----------------------------------------------------------------------
-Charter for the devel-cvs mailing list:
-
-The CVS Developers' List <dev@ccvs.cvshome.org> exists to help people
-with access to the CVS source repository co-ordinate changes, make
-releases, and administer the repository.
-
-Everyone who has been given checkin access to the repository for the
-CVS sources should read devel-cvs.  Only those with checkin access may
-send messages to the list.
-
-The devel-cvs list may be used to discuss:
-- administrivia regarding the CVS source repository and release
-  process, and
-- changes and features intended for inclusion in the official CVS
-  release (either source code or documentation), which someone plans
-  to implement, or has implemented.
-
-The devel-cvs list should not be used to discuss:
-- changes or features to packages other than the CVS release
-  (e.g., related packages like tkCVS, RAD/CVS, or other groups'
-  distributions of CVS, like RCVS, etc.),
-- changes which nobody has offered to implement, or
-- the philosophy of CVS (as opposed to a specific change to CVS).
-These topics should either go on info-cvs, or have a new mailing list
-created for them.
-
-The topic restrictions in this charter do not reflect the development
-group's future plans for CVS; rather, they reflect a topic
-classification which the group finds helpful.
-
-----------------------------------------------------------------------
 Policies regarding the CVS source repository:
 
 By checking items into the repository, developers agree to permit