[Savannah-cvs] [220] replace broken links to manual et al.; Davin Pearson mail to savannah-register-public, 16 Aug 2016 20:17:46

[karl]

Revision: 220
          
http://svn.sv.gnu.org/viewvc/?view=rev&root=administration&revision=220
Author:   karl
Date:     2016-09-05 16:04:18 +0000 (Mon, 05 Sep 2016)
Log Message:
-----------
replace broken links to manual et al.; Davin Pearson mail to 
savannah-register-public, 16 Aug 2016 20:17:46

Modified Paths:
--------------
    trunk/sviki/CvsGettingStarted.mdwn

Modified: trunk/sviki/CvsGettingStarted.mdwn
===================================================================
--- trunk/sviki/CvsGettingStarted.mdwn  2016-09-02 15:40:33 UTC (rev 219)
+++ trunk/sviki/CvsGettingStarted.mdwn  2016-09-05 16:04:18 UTC (rev 220)
@@ -1,13 +1,19 @@
-1.  Firstly, note that this FAQ is concerned only with accessing the
+Getting started with CVS
+========================
+
+0.  First, note that this FAQ is concerned only with accessing the
     repositories for projects on which you are a developer. If you
     simply want to check out code for a project and don't need to commit
     changes back, you should use anonymous access.
-2.  Make sure you have correctly registered an SSH key for your machine
+
+0.  Make sure you have correctly registered an SSH key for your machine
     with Savannah, as explained in [[SshAccess]].
-3.  Move into the local directory where you want to keep your local copy
+
+0.  Move into the local directory where you want to keep your local copy
     of the CVS tree. For example:
     `         mkdir ~/myproj-workingdir         cd ~/myproj-workingdir     `
-4.  Download the CVS tree structure as explained in your project's CVS
+
+0.  Download the CVS tree structure as explained in your project's CVS
     page (for example,
     <https://savannah.gnu.org/cvs/?group=emacs>)
     under "Project Member CVS Access via SSH".
@@ -20,7 +26,7 @@
     that you are not using the -P (prune directory) option in your
     command line or \~/.cvsrc file.
 
-5.  You can now start creating any files you want in your local project
+0.  You can now start creating any files you want in your local project
     directory (\~/myproj-workingdir/project in the example above). Every
     time you create a new file, you must add it and commit it to the
     repository with:
@@ -47,17 +53,16 @@
 
     `           cvs ci filename     `
 
-6.  You can see the contents and history of your CVS repository via the
+0.  You can see the contents and history of your CVS repository via the
     ViewCVS interface. There are links to this interface in your project
     page.
 
-    You may want to use a frontend to CVS; we recommend tkcvs, see
+0.  You may want to use a frontend to CVS; we recommend tkcvs, see
     <http://www.gnu.org/directory/TkCVS.html>
 
-    For more info, read
-    <http://www.freenix.org/unix/linux/HOWTO-vo/CVS-RCS-HOWTO.html>
-
-    You can also read the man page for cvs or the "Quick reference to
-    CVS"
-    (<http://ximbiot.com/cvs/manual/cvs-1.11.19/cvs_17.html>
-    (node "Invoking CVS" in the info file)
+    More info (and sources):
+    - <http://linuxdocs.org/HOWTOs/CVS-RCS-HOWTO.html>
+    - <http://www.cs.umb.edu/~srevilak/cvs.html>
+    - <http://ftp.gnu.org/non-gnu/cvs/source/stable/1.11.23/>
+    - <http://ftp.gnu.org/non-gnu/cvs/source/feature/1.12.13/>
+    - node "Invoking CVS" in the Info system.