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

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

details:   https://anonhg.NetBSD.org/src/rev/52db8e50e77c
branches:  trunk
changeset: 448860:52db8e50e77c
user:      gutteridge <gutteridge%NetBSD.org@localhost>
date:      Tue Feb 12 01:32:08 2019 +0000

description:
cvs.1 & cvs.texinfo: add information about the "update" command's "-t"
flag to cvs.texinfo, so the installed man and info documentation match
here. This makes cvs.1 auto-generable from cvs.texinfo again, which I
plan to leverage with further additions later.

diffstat:

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

diffs (88 lines):

diff -r 0d056803f33e -r 52db8e50e77c external/gpl2/xcvs/dist/doc/cvs.1
--- a/external/gpl2/xcvs/dist/doc/cvs.1 Mon Feb 11 20:40:18 2019 +0000
+++ b/external/gpl2/xcvs/dist/doc/cvs.1 Tue Feb 12 01:32:08 2019 +0000
@@ -3900,7 +3900,7 @@
 .IP "\(bu" 2
 Changes: working directory.
 .SP
-After you\(aqve run checkout to create your private copy
+After you\(aqve run \fBcheckout\fR to create your private copy
 of source from the common repository, other developers
 will continue changing the central source.  From time
 to time, when it is convenient in your development
@@ -3954,19 +3954,6 @@
 Prune empty directories.  See see node `Moving directories\(aq in the CVS manual.
 .SP
 .IP "" 0
-\fB-t\fR
-.IP "" 2
-Preserve source timestamps.  Unlike \fBcheckout\fR where files are created
-using the original timestamp of the file in the repository, \fBupdate\fR
-updates files using the current time of the machine.  This is convenient
-because updated files appear newer than any other files on the system so
-.BR make ( 1 )
-knows that are their corresponding built artifacts are out of date and
-they will get rebuilt.  The \fB-t\fR flag instead preserves the timestamps
-of the original repository files, behaving exactly like \fBcheckout\fR.
-This is useful for maintaining a tree in the original checked-out state.
-.SP
-.IP "" 0
 \fB-p\fR
 .IP "" 2
 Pipe files to the standard output.
@@ -3986,6 +3973,18 @@
 See see node `Sticky tags\(aq in the CVS manual, for more information on sticky tags/dates. Also
 see see node `Common options\(aq in the CVS manual.
 .SP
+.IP "" 0
+\fB-t\fR
+.IP "" 2
+Preserve source timestamps.  Unlike \fBcheckout\fR, where files are created
+using the original timestamp of the file in the repository, \fBupdate\fR
+updates files using the current time of the machine.  This is convenient
+because updated files appear newer than any other files on the system so
+\fBmake(1)\fR knows that their corresponding built artifacts are out of date
+and they will get rebuilt.  The \fB-t\fR flag instead preserves the timestamps
+of the original repository files, behaving exactly like \fBcheckout\fR.
+This is useful for maintaining a tree in the original checked-out state.
+.SP
 These special options are also available with
 \fBupdate\fR.
 .SP
diff -r 0d056803f33e -r 52db8e50e77c external/gpl2/xcvs/dist/doc/cvs.texinfo
--- a/external/gpl2/xcvs/dist/doc/cvs.texinfo   Mon Feb 11 20:40:18 2019 +0000
+++ b/external/gpl2/xcvs/dist/doc/cvs.texinfo   Tue Feb 12 01:32:08 2019 +0000
@@ -11595,14 +11595,14 @@
 
 @itemize @bullet
 @item
-update [-ACdflPpR] [-I name] [-j rev [-j rev]] [-k kflag] [-r tag[:date] | -D date] [-W spec] files@dots{}
+update [-ACdflPpRt] [-I name] [-j rev [-j rev]] [-k kflag] [-r tag[:date] | -D date] [-W spec] files@dots{}
 @item
 Requires: repository, working directory.
 @item
 Changes: working directory.
 @end itemize
 
-After you've run checkout to create your private copy
+After you've run @code{checkout} to create your private copy
 of source from the common repository, other developers
 will continue changing the central source.  From time
 to time, when it is convenient in your development
@@ -11666,6 +11666,16 @@
 existed on @var{date}.  This option is sticky, and implies @samp{-P}.
 See @ref{Sticky tags}, for more information on sticky tags/dates. Also
 see @ref{Common options}.
+
+@item -t
+Preserve source timestamps.  Unlike @code{checkout}, where files are created
+using the original timestamp of the file in the repository, @code{update}
+updates files using the current time of the machine.  This is convenient
+because updated files appear newer than any other files on the system so
+@code{make(1)} knows that their corresponding built artifacts are out of date
+and they will get rebuilt.  The @samp{-t} flag instead preserves the timestamps
+of the original repository files, behaving exactly like @code{checkout}.
+This is useful for maintaining a tree in the original checked-out state.
 @end table
 
 @need 800