[Savannah-cvs] [64] Document how to disable cvs commits.

[Bob Proulx]

Revision: 64
          http://svn.sv.gnu.org/viewvc/?view=rev&root=administration&revision=64
Author:   rwp
Date:     2014-02-09 21:42:51 +0000 (Sun, 09 Feb 2014)
Log Message:
-----------
Document how to disable cvs commits.

Added Paths:
-----------
    trunk/sviki/CvsDisabling.mdwn

Added: trunk/sviki/CvsDisabling.mdwn
===================================================================
--- trunk/sviki/CvsDisabling.mdwn                               (rev 0)
+++ trunk/sviki/CvsDisabling.mdwn       2014-02-09 21:42:51 UTC (rev 64)
@@ -0,0 +1,26 @@
+Disabling CVS Access
+====================
+
+If a project has moved from CVS to a different version control system
+we typically leave the previous cvs repository online.  Disk space
+isn't usually a concern.  Sometimes the conversion is not complete and
+it is useful to have the original cvs sources available for
+comparison, and sometimes for a repeat conversion attempt.
+
+But since the main branch of development has moved elsewhere we don't
+want people to be confused and to commit to the prior version control
+repository by mistake.  When a project has moved away from cvs it is
+useful to disable commits to the cvs repository.
+
+This can be done by inserting the following rule into the project's
+CVSROOT/commitinfo file.  It will call the commit_obsolete_notice
+script which will notify the committer of the current status.  The
+script exits non-zero which will cause cvs to abort the commit.
+
+    ALL /usr/local/bin/commit\_obsolete\_notice %r/%p %s
+
+Note: The %r/%p %s parameters are not used by the script.  If they are
+missing cvs complains that they are missing.  (That was a previous
+default setting that was removed as a cvs default.)  Therefore it is
+easier to ensure that the parameters are there so as to keep cvs
+silent about them.