Import cvs-1.11.22 onto vendor branch.

1 files changed, 54 insertions, 30 deletions

diff --git a/contrib/cvs/HACKING b/contrib/cvs/HACKING
index 5466da2..9755591 100644
--- a/contrib/cvs/HACKING
+++ b/contrib/cvs/HACKING
@@ -1,10 +1,29 @@
 How to write code for CVS
 
+* License of CVS
+
+    CVS is Copyright (C) 1989-2005 The Free Software Foundation, Inc.
+
+    This program is free software; you can redistribute it and/or modify
+    it under the terms of the GNU General Public License as published by
+    the Free Software Foundation; either version 1, or (at your option)
+    any later version.
+
+    More details are available in the COPYING file but, in simplified
+    terms, this means that any distributed modifications you make to
+    this software must also be released under the GNU General Public
+    License.
+
+    This program is distributed in the hope that it will be useful,
+    but WITHOUT ANY WARRANTY; without even the implied warranty of
+    MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+    GNU General Public License for more details.
+
 * Source
 
 Patches against the development version of CVS are most likely to be accepted:
 
-	$ cvs -d:pserver:anoncvs@cvs.cvshome.org/cvsroot co ccvs
+    $ CVS_RSH=ssh cvs -d:ext:anoncvs@savannah.nongnu.org:/cvsroot/cvs co ccvs
 
 * Compiler options
 
@@ -13,13 +32,28 @@ detect many programming errors.  This is not the default because it
 might cause spurious warnings, but at least on some machines, there
 should be no spurious warnings.  For example:
 
-	$ CFLAGS="-g -Wall" ./configure
+    $ CFLAGS="-g -Wall" ./configure
 
 Configure is not very good at remembering this setting; it will get
 wiped out whenever you do a ./config.status --recheck, so you'll need
 to use:
 
-	$ CFLAGS="-g -Wall" ./config.status --recheck
+    $ CFLAGS="-g -Wall" ./config.status --recheck
+
+* Backwards Compatibility
+
+Only bug fixes are accepted into the stable branch.  New features should be
+applied to the trunk.
+
+If it is not inextricable from a bug fix, CVS's output (to stdout/stderr)
+should not be changed on the stable branch in order to best support scripts and
+other tools which parse CVS's output.  It is ok to change output between
+feature releases (on the trunk), though such changes should be noted in the
+NEWS file.
+
+Changes in the way CVS responds to command line options, config options, etc.
+should be accompanied by deprecation warnings for an entire stable series of
+releases before being changed permanently, if at all possible.
 
 * Indentation style
 
@@ -100,10 +134,6 @@ Generally speaking the GNU coding standards are mostly used by CVS
 and perhaps an exception or two we haven't mentioned).  This is the
 file standards.text at the GNU FTP sites.
 
-Filenames for .c and .h files may contain _ but should not contain -
-(the latter causes Visual C++ 2.1 to create makefiles which Visual C++
-4.0 cannot use).
-
 * Regenerating Build Files
 
 On UNIX, if you wish to change the Build files, you will need Autoconf and
@@ -115,13 +145,13 @@ have the same versions the developers do, so the rules to run them
 automatically aren't included in the generated Makefiles unless you run
 configure with the --enable-maintainer-mode option.
 
-The CVS Makefiles and configure script were built using Automake 1.7.9 and
-Autoconf 2.58, respectively.
+The CVS Makefiles and configure script were built using Automake 1.9.6 and
+Autoconf 2.59, respectively.
 
 There is a known bug in Autoconf 2.57 that will prevent the configure
 scripts it generates from working on some platforms.  Other combinations of
 autotool versions may or may not work.  If you get other versions to work,
-please send a report to <bug-cvs@gnu.org>.
+please send a report to <bug-cvs@nongnu.org>.
 
 * Writing patches (strategy)
 
@@ -174,7 +204,7 @@ for each issue.  Use context diffs or unidiffs for patches.
 
 Include words like "I grant permission to distribute this patch under
 the terms of the GNU Public License" with your patch.  By sending a
-patch to bug-cvs@gnu.org, you implicitly grant this permission.
+patch to bug-cvs@nongnu.org, you implicitly grant this permission.
 
 Submitting a patch to bug-cvs is the way to reach the people who have
 signed up to receive such submissions (including CVS developers), but
@@ -203,27 +233,21 @@ intentional, to avoid a last minute rush to get new features in.
 
 * Mailing lists
 
-Anyone can add themselves to the following mailing lists:
+In addition to the mailing lists listed in the README file, developers should
+take particular note of the following mailling lists:
 
-    dev.  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.
-    cvs.  The only messages sent to this list are sent
+    bug-cvs:  This is the list which users are requested to send bug reports
+      to.  General CVS development and design discussions also take place on
+      this list.
+    info-cvs:  This list is intended for user questions, but general CVS
+      development and design discussions sometimes take place on this list.
+    cvs-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
+    cvs-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 dev, cvs, or test-results, send
-a message to "<list>-subscribe@ccvs.cvshome.org" or visit
-http://ccvs.cvshome.org/servlets/ProjectMailingListList and follow the
-instructions there.
-
-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@gnu.org.
-
-Other CVS discussions take place on the info-cvs mailing list
-(send mail to info-cvs-request@gnu.org to subscribe) or on
-the newsgroup comp.software.config-mgmt.
+
+To subscribe to any of these lists, send mail to <list>-request@nongnu.org
+or visit http://savannah.nongnu.org/mail/?group=cvs and follow the instructions
+for the list you wish to subscribe to.