changeset 6:7e9df200a0b8

cvsps.1: Remove trailing whitespaces.
author ng0 <ng0@crash.cx>
date Thu, 22 Feb 2018 16:00:19 +0000
parents 29ef8e0f8e49
children 8227c5f79291
files cvsps.1
diffstat 1 files changed, 10 insertions(+), 10 deletions(-) [+]
line wrap: on
line diff
--- a/cvsps.1	Thu Feb 22 15:56:56 2018 +0000
+++ b/cvsps.1	Thu Feb 22 16:00:19 2018 +0000
@@ -3,7 +3,7 @@
 CVSps \- create patchset information from CVS
 .SH SYNOPSIS
 .B cvsps
-[\-h] [\-x] [\-u] [\-z <fuzz>] [\-g] [\-s <patchset>] [\-a <author>] [\-f <file>] [\-d <date1> [\-d <date2>]] [\-l <text>] [\-b <branch>] [\-r <tag> [\-r <tag>]] [\-p <directory>] [\-v] [\-t] [\-\-norc] [\-\-summary\-first] [\-\-test\-log <filename>] [\-\-bkcvs] [\-\-no\-rlog] [\-\-diff\-opts <option string>] [\-\-cvs\-direct] [\-\-debuglvl <bitmask>] [\-Z <compression>] [\-\-root <cvsroot>] [\-q] [\-A] [<repository>] 
+[\-h] [\-x] [\-u] [\-z <fuzz>] [\-g] [\-s <patchset>] [\-a <author>] [\-f <file>] [\-d <date1> [\-d <date2>]] [\-l <text>] [\-b <branch>] [\-r <tag> [\-r <tag>]] [\-p <directory>] [\-v] [\-t] [\-\-norc] [\-\-summary\-first] [\-\-test\-log <filename>] [\-\-bkcvs] [\-\-no\-rlog] [\-\-diff\-opts <option string>] [\-\-cvs\-direct] [\-\-debuglvl <bitmask>] [\-Z <compression>] [\-\-root <cvsroot>] [\-q] [\-A] [<repository>]
 .SH DESCRIPTION
 CVSps is a program for generating 'patchset' information from a CVS
 repository.  A patchset in this case is defined as a set of changes made
@@ -116,14 +116,14 @@
 of this is that after this patchset, every revision of every file is after
 the tag (and conversely, before this patchset, at least one file is still
 before the tag).  However, there are two kinds of inconsistent (or 'funky')
-tags that can be created, even when following best practices for cvs.  
+tags that can be created, even when following best practices for cvs.
 .PP
 The first
 is what is called a FUNKY tag.  A funky tag is one where there are patchsets
 which are chronologically (and thus by patchset id) earlier than the tag, but
 are tagwise after.  These tags will be marked as '**FUNKY**' in the Tag: section
 of the cvsps output.  When a funky tag is specified as one of the '\-r' arguments,
-there are some number of patchsets which need to be considered out of sequence.  
+there are some number of patchsets which need to be considered out of sequence.
 In this case, the patchsets themselves will be labeled FUNKY and will be processed
 correctly.
 .PP
@@ -132,14 +132,14 @@
 but which have members which are tagwise both before, and after the tag, in the
 same patchset.  If an INVALID tag is specified as one of the '\-r' arguments,
 cvsps will flag each member of the affected patchsets as before or after the tag
-and the patchset summary will indicate which members are which, and diffs will 
+and the patchset summary will indicate which members are which, and diffs will
 be generated accordingly.
 .SH "NOTE ON CVS VERSIONS"
 Among the different cvs subcommands used by cvsps is the 'rlog' command.  The
 rlog command is used to get revision history of a module, and it disregards
 the current working directory.  The important difference between 'rlog' and 'log'
 (from cvsps perspective) is the 'rlog' will include log data for files not in
-the current working directory.  The impact of this is mainly when there are 
+the current working directory.  The impact of this is mainly when there are
 directories which at one time had files, but are now empty, and have been pruned
 from the working directory with the '\-P' option.  If 'rlog' is not used, these
 files logs will not be parsed, and the PatchSet numbering will be unstable.
@@ -153,12 +153,12 @@
 Another important note is that cvsps will attempt, whenever possible, to use the
 r\-commands (rlog, rdiff  and co) instead of the local commands (log, diff, and update).
 This is to allow cvsps to function without a completely checked out tree.  Because
-these r\-commands are used, the generated diffs will include the module directory in 
+these r\-commands are used, the generated diffs will include the module directory in
 them, and it is recommended to apply them in the working directory with the \-p1 option
-to the patch command.  However, if the \-\-diff\-opts option is specified (to change, for 
+to the patch command.  However, if the \-\-diff\-opts option is specified (to change, for
 example, the lines of context), then rdiff cannot be used, because it doesn't support
 arbitrary options.  In this case, the patches will be generated without the module
-directory in the path, and \-p0 will be required when applying the patch.  When 
+directory in the path, and \-p0 will be required when applying the patch.  When
 diffs are generated in cvs\-direct mode (see below), however, they will always
 be \-p1 style patches.
 .SH "NOTE ON BKCVS"
@@ -169,13 +169,13 @@
 file is being created or updated (i.e. initial run of cvsps, or when \-u and \-x options
 are used).
 .SH "NOTE ON CVS\-DIRECT"
-As of version 2.0b6 cvsps has a partial implementation of the cvs client code built 
+As of version 2.0b6 cvsps has a partial implementation of the cvs client code built
 in.  This reduces the RTT and/or handshaking overhead from one per patchset member
 to one per patchset.  This dramatically increases the speed of generating diffs
 over a slow link, and improves the consistency of operation.  Currently the \-\-cvs\-direct
 option turns on the use of this code, but it very well may be default by the time
 2.0 comes out.  The built\-in cvs code attempts to be compatible with cvs, but may
-have problems, which should be reported.  It honors the CVS_RSH and CVS_SERVER 
+have problems, which should be reported.  It honors the CVS_RSH and CVS_SERVER
 environment variables, but does not parse the ~/.cvsrc file.
 .SH "NOTE ON CVSPS RC FILE"
 CVSps parses an rc file at startup.  This file should be located in ~/.cvsps/cvspsrc.