Latest from Cyclic Software

1 files changed, 29 insertions, 29 deletions

diff --git a/gnu/usr.bin/cvs/doc/cvs.info-1 b/gnu/usr.bin/cvs/doc/cvs.info-1
index 7bf742bcffc..e3f816d961e 100644
--- a/gnu/usr.bin/cvs/doc/cvs.info-1
+++ b/gnu/usr.bin/cvs/doc/cvs.info-1
@@ -1,4 +1,4 @@
-This is cvs.info, produced by Makeinfo version 3.12f from ./cvs.texinfo.
+This is cvs.info, produced by makeinfo version 4.0 from ./cvs.texinfo.
 
 START-INFO-DIR-ENTRY
 * CVS: (cvs).          Concurrent Versions System
@@ -27,7 +27,7 @@ File: cvs.info,  Node: Top,  Next: Overview,  Up: (dir)
 
 
    This info manual describes how to use and administer CVS version
-1.10.7.
+1.11.
 
 * Menu:
 
@@ -123,7 +123,7 @@ support.
 the internet.  For more information on downloading CVS and other CVS
 topics, see:
 
-     http://www.cyclic.com/
+     http://www.cvshome.org/
      http://www.loria.fr/~molli/cvs-index.html
 
    There is a mailing list, known as `info-cvs', devoted to CVS.  To
@@ -218,7 +218,7 @@ CVS does not have change control
      reported bugs and the status of each one (is it fixed?  in what
      release?  has the bug submitter agreed that it is fixed?).  For
      interfacing CVS to an external bug-tracking system, see the
-     `rcsinfo' and `verifymsg' files (*note Administrative files::.).
+     `rcsinfo' and `verifymsg' files (*note Administrative files::).
 
      Another aspect of change control is keeping track of the fact that
      changes to several files were in fact changed together as one
@@ -262,7 +262,7 @@ A sample session
 
    As a way of introducing CVS, we'll go through a typical work-session
 using CVS.  The first thing to understand is that CVS stores all files
-in a centralized "repository" (*note Repository::.); this section
+in a centralized "repository" (*note Repository::); this section
 assumes that a repository is set up.
 
    Suppose you are working on a simple compiler.  The source consists
@@ -362,7 +362,7 @@ copy of tc.  One acceptable way to do that is of course
      $ cd ..
      $ rm -r tc
 
-but a better way is to use the `release' command (*note release::.):
+but a better way is to use the `release' command (*note release::):
 
      $ cd ..
      $ cvs release -d tc
@@ -528,8 +528,8 @@ the repository via CVS commands, such changes need not be disruptive.
 
    However, in some cases it may be necessary to understand how CVS
 stores data in the repository, for example you might need to track down
-CVS locks (*note Concurrency::.) or you might need to deal with the
-file permissions appropriate for the repository.
+CVS locks (*note Concurrency::) or you might need to deal with the file
+permissions appropriate for the repository.
 
 * Menu:
 
@@ -642,7 +642,7 @@ group that owns the directory.
 per-directory basis.
 
    Note that users must also have write access to check out files,
-because CVS needs to create lock files (*note Concurrency::.).
+because CVS needs to create lock files (*note Concurrency::).
 
    Also note that users must have write access to the
 `CVSROOT/val-tags' file.  CVS uses it to keep track of what tags are
@@ -662,16 +662,16 @@ and/or files in the repository.  `CVSUMASK' does not affect the file
 permissions in the working directory; such files have the permissions
 which are typical for newly created files, except that sometimes CVS
 creates them read-only (see the sections on watches, *Note Setting a
-watch::; -r, *Note Global options::; or CVSREAD, *Note Environment
+watch::; -r, *Note Global options::; or `CVSREAD', *Note Environment
 variables::).
 
-   Note that using the client/server CVS (*note Remote
-repositories::.), there is no good way to set `CVSUMASK'; the setting
-on the client machine has no effect.  If you are connecting with `rsh',
-you can set `CVSUMASK' in `.bashrc' or `.cshrc', as described in the
-documentation for your operating system.  This behavior might change in
-future versions of CVS; do not rely on the setting of `CVSUMASK' on the
-client having no effect.
+   Note that using the client/server CVS (*note Remote repositories::),
+there is no good way to set `CVSUMASK'; the setting on the client
+machine has no effect.  If you are connecting with `rsh', you can set
+`CVSUMASK' in `.bashrc' or `.cshrc', as described in the documentation
+for your operating system.  This behavior might change in future
+versions of CVS; do not rely on the setting of `CVSUMASK' on the client
+having no effect.
 
    Using pserver, you will generally need stricter permissions on the
 CVSROOT directory and directories above it in the tree; see *Note
@@ -894,9 +894,9 @@ CVS should print
      cvs commit: Rebuilding administrative file database
 
 and update the checked out copy in `$CVSROOT/CVSROOT'.  If it does not,
-there is something wrong (*note BUGS::.).  To add your own files to the
+there is something wrong (*note BUGS::).  To add your own files to the
 files to be updated in this fashion, you can add them to the
-`checkoutlist' administrative file (*note checkoutlist::.).
+`checkoutlist' administrative file (*note checkoutlist::).
 
    By default, the `modules' file behaves as described above.  If the
 modules file is very large, storing it as a flat text file may make
@@ -997,15 +997,15 @@ by CVS probably will not be portable between such systems either.
      timestamp of the file and simply do a string compare with
      TIMESTAMP.  If there was a conflict, CONFLICT can be set to the
      modification time of the file after the file has been written with
-     conflict markers (*note Conflicts example::.).  Thus if CONFLICT
-     is subsequently the same as the actual modification time of the
-     file it means that the user has obviously not resolved the
-     conflict.  OPTIONS contains sticky options (for example `-kb' for a
-     binary file).  TAGDATE contains `T' followed by a tag name, or `D'
-     for a date, followed by a sticky tag or date.  Note that if
-     TIMESTAMP contains a pair of timestamps separated by a space,
-     rather than a single timestamp, you are dealing with a version of
-     CVS earlier than CVS 1.5 (not documented here).
+     conflict markers (*note Conflicts example::).  Thus if CONFLICT is
+     subsequently the same as the actual modification time of the file
+     it means that the user has obviously not resolved the conflict.
+     OPTIONS contains sticky options (for example `-kb' for a binary
+     file).  TAGDATE contains `T' followed by a tag name, or `D' for a
+     date, followed by a sticky tag or date.  Note that if TIMESTAMP
+     contains a pair of timestamps separated by a space, rather than a
+     single timestamp, you are dealing with a version of CVS earlier
+     than CVS 1.5 (not documented here).
 
      The timezone on the timestamp in CVS/Entries (local or universal)
      should be the same as the operating system stores for the
@@ -1116,6 +1116,6 @@ by CVS probably will not be portable between such systems either.
 
 `Template'
      This file contains the template specified by the `rcsinfo' file
-     (*note rcsinfo::.).  It is only used by the client; the
+     (*note rcsinfo::).  It is only used by the client; the
      non-client/server CVS consults `rcsinfo' directly.