summaryrefslogtreecommitdiff
path: root/gnu/usr.bin/cvs/HACKING
diff options
context:
space:
mode:
Diffstat (limited to 'gnu/usr.bin/cvs/HACKING')
-rw-r--r--gnu/usr.bin/cvs/HACKING30
1 files changed, 29 insertions, 1 deletions
diff --git a/gnu/usr.bin/cvs/HACKING b/gnu/usr.bin/cvs/HACKING
index 6ccd4f9f4b4..89f7399e0e0 100644
--- a/gnu/usr.bin/cvs/HACKING
+++ b/gnu/usr.bin/cvs/HACKING
@@ -133,7 +133,8 @@ the code are appropriate for this, but not always)--patches should not
be checked in unless there is some reason for them, and the
description may be helpful if there is a better way to solve the
problem. In addition to the ChangeLog entry, there should be a change
-to the NEWS file and cvs.texinfo in the case of a user-visible change.
+to the NEWS file and cvs.texinfo, if the change is a user-visible
+change worth mentioning.
It is nice to have a test case (see TESTS), especially for fixes which
involve subtle behaviors or twisted sections of the code.
@@ -162,3 +163,30 @@ even hinted at, really) until the feature freeze which is
approximately 2 weeks before the final release (at this time test
releases start appearing and are announced on info-cvs). This is
intentional, to avoid a last minute rush to get new features in.
+
+* Mailing lists
+
+Anyone can add themselves to the following mailing lists:
+
+ devel-cvs. Unless you are accepted as a CVS developer as
+ described in the DEVEL-CVS file, you will only be able to
+ read this list, not send to it. The charter of the list is
+ also in DEVEL-CVS.
+ commit-cvs. The only messages sent to this list are sent
+ automatically, via the CVS `loginfo' mechanism, when someone
+ checks something in to the master CVS repository.
+ test-results. The only messages sent to this list are sent
+ automatically, daily, by a script which runs "make check"
+ and "make remotecheck" on the master CVS sources.
+To subscribe to devel-cvs, commit-cvs, or test-results, send
+a message to "majordomo@cyclic.com" whose body consists of
+"subscribe <list>", where <list> is devel-cvs, commit-cvs or
+test-results.
+
+One other list related to CVS development is bug-cvs. This is the
+list which users are requested to send bug reports to. Anyone can
+subscribe; to do so send mail to bug-cvs-request@prep.ai.mit.edu.
+
+Other CVS discussions take place on the info-cvs mailing list
+(send mail to info-cvs-request@prep.ai.mit.edu to subscribe) or on
+the newsgroup comp.software.config-mgmt.