[src/trunk]: src/external/gpl2/xcvs/dist/doc Fix the build by merging duplica...

[christos <christos%NetBSD.org@localhost>]

details:   https://anonhg.NetBSD.org/src/rev/eaf556171eb6
branches:  trunk
changeset: 449299:eaf556171eb6
user:      christos <christos%NetBSD.org@localhost>
date:      Sun Mar 03 02:21:07 2019 +0000

description:
Fix the build by merging duplicate "init" sections.

diffstat:

 external/gpl2/xcvs/dist/doc/cvs.texinfo |  41 ++++++++++++--------------------
 1 files changed, 16 insertions(+), 25 deletions(-)

diffs (67 lines):

diff -r 8b958c282aac -r eaf556171eb6 external/gpl2/xcvs/dist/doc/cvs.texinfo
--- a/external/gpl2/xcvs/dist/doc/cvs.texinfo   Sat Mar 02 21:30:40 2019 +0000
+++ b/external/gpl2/xcvs/dist/doc/cvs.texinfo   Sun Mar 03 02:21:07 2019 +0000
@@ -1939,26 +1939,6 @@
 which one only has read access to; @sc{cvs} needs to be
 able to create lock files (@pxref{Concurrency}).
 
-@cindex init (subcommand)
-To create a repository, run the @code{cvs init}
-command.  It will set up an empty repository in the
-@sc{cvs} root specified in the usual way
-(@pxref{Repository}).  For example,
-
-@example
-cvs -d /usr/local/cvsroot init
-@end example
-
-@code{cvs init} is careful to never overwrite any
-existing files in the repository, so no harm is done if
-you run @code{cvs init} on an already set-up
-repository. Note you may need to be a member of the
-group @code{cvsadmin} to do this.
-
-@code{cvs init} will enable history logging; if you
-don't want that, remove the history file after running
-@code{cvs init}.  @xref{history file}.
-
 @node Backing up
 @section Backing up a repository
 @cindex Repository, backing up
@@ -10875,7 +10855,7 @@
 
 @itemize @bullet
 @item
-init
+Synopsis: init
 @item
 Requires: working directory.
 @item
@@ -10886,12 +10866,23 @@
 @file{CVSROOT} subdirectory and some default control files. You must
 use this command or initialize the repository in some other way before
 you can use it. Specify the root of the repository with the general
-@code{-d} option.
+@code{-d} option.  This will set up an empty repository in the
+@sc{cvs} root specified in the usual way (@pxref{Repository}).
+For example,
+
+@code{cvs init} is careful to never overwrite any
+existing files in the repository, so no harm is done if
+you run @code{cvs init} on an already set-up
+repository. Note you may need to be a member of the
+group @code{cvsadmin} to do this.
 
 Note @code{init} will enable history logging; if you don't want that,
-remove the history file after running @code{init}.
-
-@c . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
+remove the history file after running @code{init}.  @xref{history file}.
+
+@menu
+* init examples:              init examples
+@end menu
+
 @node init examples
 @appendixsubsec init examples