Source-Changes-HG archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

[src/trunk]: src/external/gpl2/xcvs/dist/doc cvs.1 & cvs.texinfo: minor amend...



details:   https://anonhg.NetBSD.org/src/rev/1908009c2dd7
branches:  trunk
changeset: 449325:1908009c2dd7
user:      gutteridge <gutteridge%NetBSD.org@localhost>
date:      Sun Mar 03 21:11:54 2019 +0000

description:
cvs.1 & cvs.texinfo: minor amendments and cvs.1 regen

Put a cross-reference to "init" back in "Creating a Repository" and
other minor formatting tweaks, and regenerate cvs.1 to reflect the
previous changes by christos@ in cvs.texinfo r. 1.7.

diffstat:

 external/gpl2/xcvs/dist/doc/cvs.1       |  12 +++++++++---
 external/gpl2/xcvs/dist/doc/cvs.texinfo |  18 ++++++++++--------
 2 files changed, 19 insertions(+), 11 deletions(-)

diffs (73 lines):

diff -r 4a166472fe3d -r 1908009c2dd7 external/gpl2/xcvs/dist/doc/cvs.1
--- a/external/gpl2/xcvs/dist/doc/cvs.1 Sun Mar 03 20:34:43 2019 +0000
+++ b/external/gpl2/xcvs/dist/doc/cvs.1 Sun Mar 03 21:11:54 2019 +0000
@@ -3086,7 +3086,7 @@
 .IX "init (subcommand)"
 .SP
 .IP "\(bu" 2
-init
+Synopsis: init
 .IP "\(bu" 2
 Requires: working directory.
 .IP "\(bu" 2
@@ -3096,10 +3096,16 @@
 \fBCVSROOT\fR 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
-\fB-d\fR option.
+\fB-d\fR option.  This will set up an empty repository in the
+\fBcvs\fR root specified in the usual way (see node `Repository\(aq in the CVS manual).
+.SP
+\fBinit\fR is careful to never overwrite any existing files in the
+repository, so no harm is done if you run \fBinit\fR on an already
+set-up repository. Note you may need to be a member of the group
+\fBcvsadmin\fR to do this.
 .SP
 Note \fBinit\fR will enable history logging; if you don\(aqt want that,
-remove the history file after running \fBinit\fR.
+remove the history file after running \fBinit\fR (see node `history file\(aq in the CVS manual).
 .SP
 .SH "init examples"
 .SP
diff -r 4a166472fe3d -r 1908009c2dd7 external/gpl2/xcvs/dist/doc/cvs.texinfo
--- a/external/gpl2/xcvs/dist/doc/cvs.texinfo   Sun Mar 03 20:34:43 2019 +0000
+++ b/external/gpl2/xcvs/dist/doc/cvs.texinfo   Sun Mar 03 21:11:54 2019 +0000
@@ -1939,6 +1939,9 @@
 which one only has read access to; @sc{cvs} needs to be
 able to create lock files (@pxref{Concurrency}).
 
+To create a repository, run the @code{cvs init}         
+command (@pxref{init}).
+
 @node Backing up
 @section Backing up a repository
 @cindex Repository, backing up
@@ -10868,21 +10871,20 @@
 you can use it. Specify the root of the repository with the general
 @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.
+
+@code{init} is careful to never overwrite any existing files in the
+repository, so no harm is done if you run @code{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}.  @xref{history file}.
+remove the history file after running @code{init} (@pxref{history file}).
 
 @menu
 * init examples:              init examples
 @end menu
 
+@c . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
 @node init examples
 @appendixsubsec init examples
 



Home | Main Index | Thread Index | Old Index