neulab/tldr huggingface dataset:
annotate options These standard options are supported by annotate (see node `Common options' in the CVS manual for a complete description of them):
Local directory only, no recursion.
Process directories recursively.
Use head revision if tag/date not found.
Annotate binary files.
-r revision
Annotate file as of specified revision/tag.
-D date
Annotate file as of specified date.
annotate example For example:
$ cvs annotate ssfile Annotations for ssfile *************** 1.1          (mary     27-Mar-96): ssfile line 1 1.2          (joe      28-Mar-96): ssfile line 2
The file ssfile currently contains two lines.  The ssfile line 1 line was checked in by mary on March 27.  Then, on March 28, joe added a line ssfile line 2, without modifying the ssfile line 1 line.  This report doesn't tell you anything about lines which have been deleted or replaced; you need to use cvs diff for that (see node `diff' in the CVS manual).
The options to cvs annotate are listed in `Invoking CVS' in the CVS manual, and can be used to select the files and revisions to annotate. The options are described in more detail there and in `Common options' in the CVS manual.
checkout Check out sources for editing • Synopsis: checkout [options] modules...
• Changes: working directory.
• Synonyms: co, get
Create or update a working directory containing copies of the source files specified by modules.  You must execute checkout before using most of the other cvs commands, since most of them operate on your working directory.
The modules are either symbolic names for some collection of source directories and files, or paths to directories or files in the repository.  The symbolic names are defined in the modules file.  See `modules' in the CVS manual.
Depending on the modules you specify, checkout may recursively create directories and populate them with the appropriate source files.  You can then edit these source files at any time (regardless of whether other software developers are editing their own copies of the sources); update them to include new changes applied by others to the source repository; or commit your work as a permanent change to the source repository.
Note that checkout is used to create directories.  The top-level directory created is always added to the directory where checkout is invoked, and usually has the same name as the specified module.  In the case of a module alias, the created sub-directory may have a different name, but you can be sure that it will be a sub-directory, and that checkout will show the relative path leading to each file as it is extracted into your private work area (unless you specify the -Q global option).
The files created by checkout are created read-write, unless the -r option to cvs (see node `Global options' in the CVS manual) is specified, the CVSREAD environment variable is specified (see node `Environment variables' in the CVS manual), or a watch is in effect for that file (see node `Watches' in the CVS manual).
Note that running checkout on a directory that was already built by a prior checkout is also permitted.  This is similar to specifying the -d option to the update command in the sense that new directories that have been created in the repository will appear in your work area. However, checkout takes a module name whereas update takes a directory name.  Also to use checkout this way it must be run from the top level directory (where you originally ran checkout from), so before you run checkout to update an existing directory, don't forget to change your directory to the top level directory.
For the output produced by the checkout command, see node `update output' in the CVS manual.
checkout options These standard options are supported by checkout (see node `Common options' in the CVS manual for a complete description of them):
Use the most recent revision no later than date.  This option is sticky, and implies -P.  See `Sticky tags' in the CVS manual for more information on sticky tags/dates.
Only useful with the -D date or -r tag flags.  If no matching revision is found, retrieve the most recent revision (instead of ignoring the file).
Process keywords according to kflag.  See `Keyword substitution' in the CVS manual.  This option is sticky; future updates of this file in this working directory will use the same kflag.  The status command can be viewed to see the sticky options.  See `Invoking CVS' in the CVS manual for more information on the status command.
Local; run only in current working directory.
Do not run any checkout program (as specified with the -o option in the modules file; see node `modules' in the CVS manual).
Prune empty directories.  See `Moving directories' in the CVS manual.
Pipe files to the standard output.
Checkout directories recursively.  This option is on by default.
Use revision tag.  This option is sticky, and implies -P.  See `Sticky tags' in the CVS manual, for more information on sticky tags/dates.
In addition to those, you can use these special command options with checkout:
Reset any sticky tags, dates, or -k options.  Does not reset sticky -k options on modified files.  See `Sticky tags' in the CVS manual for more information on sticky tags/dates.
Copy the module file, sorted, to the standard output, instead of creating or modifying any files or directories in your working directory.
-d dir
Create a directory called dir for the working files, instead of using the module name.  In general, using this flag is equivalent to using mkdir dir; cd dir followed by the checkout command without the -d flag.
There is an important exception, however.  It is very convenient when checking out a single item to have the output appear in a directory that doesn't contain empty intermediate directories.  In this case only, cvs tries to ``shorten'' pathnames to avoid those empty directories.
For example, given a module foo that contains the file bar.c, the command cvs co -d dir foo will create directory dir and place bar.c inside.  Similarly, given a module bar which has subdirectory baz wherein there is a file quux.c, the command cvs co -d dir bar/baz will create directory dir and place quux.c inside.
Using the -N flag will defeat this behavior.  Given the same module definitions above, cvs co -N -d dir foo will create directories dir/foo and place bar.c inside, while cvs co -N -d dir bar/baz will create directories dir/bar/baz and place quux.c inside.
-j tag
With two -j options, merge changes from the revision specified with the first -j option to the revision specified with the second j option, into the working directory.
With one -j option, merge changes from the ancestor revision to the revision specified with the -j option, into the working directory.  The ancestor revision is the common ancestor of the revision which the working directory is based on, and the revision specified in the -j option.
In addition, each -j option can contain an optional date specification which, when used with branches, can limit the chosen revision to one within a specific date.  An optional date is specified by adding a colon (:) to the tag: -jSymbolic_Tag:Date_Specifier.
See `Branching and merging' in the CVS manual.
Only useful together with -d dir.  With this option, cvs will not ``shorten'' module paths in your working directory when you check out a single module.  See the -d flag for examples and a discussion.
Like -c, but include the status of all modules, and sort it by the status string.  See `modules' in the CVS manual, for info about the -s option that is used inside the modules file to set the module status.
checkout examples Get a copy of the module tc:
$ cvs checkout tc
Get a copy of the module tc as it looked one day ago:
$ cvs checkout -D yesterday tc
commit Check files into the repository • Synopsis: commit [-lRf] [-m 'log_message' | -F file] [-r revision] [files...]
• Requires: working directory, repository.
• Synonym: ci
Use commit when you want to incorporate changes from your working source files into the source repository.
If you don't specify particular files to commit, all of the files in your working current directory are examined.  commit is careful to change in the repository only those files that you have really changed. By default (or if you explicitly specify the -R option), files in subdirectories are also examined and committed if they have changed; you can use the -l option to limit commit to the current directory only.
commit verifies that the selected files are up to date with the current revisions in the source repository; it will notify you, and exit without committing, if any of the specified files must be made current first with update (see node `update' in the CVS manual).  commit does not call the update command for you, but rather leaves that for you to do when the time is right.
When all is well, an editor is invoked to allow you to enter a log message that will be written to one or more logging programs (see node `modules' in the CVS manual, and see node `loginfo' in the CVS manual) and placed in the rcs file inside the repository.  This log message can be retrieved with the log command; see node `log' in the CVS manual. You can specify the log message on the command line with the -m message option, and thus avoid the editor invocation, or use the -F file option to specify that the argument file contains the log message.
commit options These standard options are supported by commit (see node `Common options' in the CVS manual for a complete description of them):
Commit directories recursively.  This is on by default.
Commit to revision.  revision must be either a branch, or a revision on the main trunk that is higher than any existing revision number (see node `Assigning revisions' in the CVS manual).  You cannot commit to a specific revision on a branch.
commit also supports these options:
-F file
Read the log message from file, instead of invoking an editor.
Note that this is not the standard behavior of the -f option as defined in `Common options' in the CVS manual.
Force cvs to commit a new revision even if you haven't made any changes to the file.  If the current revision of file is 1.7, then the following two commands are equivalent:
$ cvs commit -f file $ cvs commit -r 1.8 file
The -f option disables recursion (i.e., it implies -l).  To force cvs to commit a new revision for all files in all subdirectories, you must use -f -R.
commit examples Committing to a branch You can commit to a branch revision (one that has an even number of dots) with the -r option.  To create a branch revision, use the -b option of the rtag or tag commands (see node `Branching and merging' in the CVS manual).  Then, either checkout or update can be used to base your sources on the newly created branch.  From that point on, all commit changes made within these working sources will be automatically added to a branch revision, thereby not disturbing main-line development in any way.  For example, if you had to create a patch to the 1.2 version of the product, even though the 2.0 version is already under development, you might do:
$ cvs rtag -b -r FCS1_2 FCS1_2_Patch product_module $ cvs checkout -r FCS1_2_Patch product_module $ cd product_module [[ hack away ]] $ cvs commit
This works automatically since the -r option is sticky.
Creating the branch after editing Say you have been working on some extremely experimental software, based on whatever revision you happened to checkout last week.  If others in your group would like to work on this software with you, but without disturbing main-line development, you could commit your change to a new branch.  Others can then checkout your experimental stuff and utilize the full benefit of cvs conflict resolution.  The scenario might look like:
[[ hacked sources are present ]] $ cvs tag -b EXPR1 $ cvs update -r EXPR1 $ cvs commit
The update command will make the -r EXPR1 option sticky on all files. Note that your changes to the files will never be removed by the update command.  The commit will automatically commit to the correct branch, because the -r is sticky.  You could also do like this:
[[ hacked sources are present ]] $ cvs tag -b EXPR1 $ cvs commit -r EXPR1
but then, only those files that were changed by you will have the -r EXPR1 sticky flag.  If you hack away, and commit without specifying the -r EXPR1 flag, some files may accidentally end up on the main trunk.
To work with you on the experimental change, others would simply do
$ cvs checkout -r EXPR1 whatever_module
diff Show differences between revisions • Synopsis: diff [-lR] [-k kflag] [format_options] [[-r rev1 | -D date1] [-r rev2 |  -D date2]] [files...]
The diff command is used to compare different revisions of files.  The default action is to compare your working files with the revisions they were based on, and report any differences that are found.
If any file names are given, only those files are compared.  If any directories are given, all files under them will be compared.
The exit status for diff is different than for other cvs commands; for details see node `Exit status' in the CVS manual.
diff options These standard options are supported by diff (see node `Common options' in the CVS manual for a complete description of them):
Use the most recent revision no later than date.  See -r for how this affects the comparison.
Process keywords according to kflag.  See `Keyword substitution' in the CVS manual.
Examine directories recursively.  This option is on by default.
Compare with revision tag.  Zero, one or two -r options can be present. With no -r option, the working file will be compared with the revision it was based on.  With one -r, that revision will be compared to your current working file.  With two -r options those two revisions will be compared (and your working file will not affect the outcome in any way).
One or both -r options can be replaced by a -D date option, described above.
The following options specify the format of the output.  They have the same meaning as in GNU diff.  Most options have two equivalent names, one of which is a single letter preceded by -, and the other of which is a long name preceded by --.
-lines
Show lines (an integer) lines of context.  This option does not specify an output format by itself; it has no effect unless it is combined with -c or -u.  This option is obsolete.  For proper operation, patch typically needs at least two lines of context.
Treat all files as text and compare them line-by-line, even if they do not seem to be text.
Ignore trailing white space and consider all other sequences of one or more white space characters to be equivalent.
Ignore changes that just insert or delete blank lines.
--binary
Read and write data in binary mode.
--brief
Report only whether the files differ, not the details of the differences.
Use the context output format.
--context[=lines]
Use the context output format, showing lines (an integer) lines of context, or three if lines is not given.  For proper operation, patch typically needs at least two lines of context.
--changed-group-format=format
Use format to output a line group containing differing lines from both files in if-then-else format.  See `Line group formats' in the CVS manual.
Change the algorithm to perhaps find a smaller set of changes.  This makes diff slower (sometimes much slower).
--ed
Make output that is a valid ed script.
--expand-tabs
Expand tabs to spaces in the output, to preserve the alignment of tabs in the input files.
Make output that looks vaguely like an ed script but has changes in the order they appear in the file.
In context and unified format, for each hunk of differences, show some of the last preceding line that matches regexp.
--forward-ed
Use heuristics to speed handling of large files that have numerous scattered small changes.
--horizon-lines=lines
Do not discard the last lines lines of the common prefix and the first lines lines of the common suffix.
Ignore changes in case; consider upper- and lower-case letters equivalent.
Ignore changes that just insert or delete lines that match regexp.
--ifdef=name
Make merged if-then-else output using name.
--ignore-all-space
Ignore white space when comparing lines.
--ignore-blank-lines
--ignore-case
Ignore changes in case; consider upper- and lower-case to be the same.
--ignore-matching-lines=regexp
--ignore-space-change
--initial-tab
Output a tab rather than a space before the text of a line in normal or context format.  This causes the alignment of tabs in the line to look normal.
-L label
Use label instead of the file name in the context format and unified format headers.
--label=label
--left-column
Print only the left column of two common lines in side by side format.
--line-format=format
Use format to output all input lines in if-then-else format.  See `Line formats' in the CVS manual.
--minimal
Output RCS-format diffs; like -f except that each command specifies the number of lines affected.
--new-file
In directory comparison, if a file is found in only one directory, treat it as present but empty in the other directory.
--new-group-format=format
Use format to output a group of lines taken from just the second file in if-then-else format.  See `Line group formats' in the CVS manual.
--new-line-format=format
Use format to output a line taken from just the second file in if-then- else format.  See `Line formats' in the CVS manual.
--old-group-format=format
Use format to output a group of lines taken from just the first file in if-then-else format.  See `Line group formats' in the CVS manual.
--old-line-format=format
Use format to output a line taken from just the first file in if-then- else format.  See `Line formats' in the CVS manual.
Show which C function each change is in.
--rcs
--report-identical-files
Report when two files are the same.
--show-c-function
--show-function-line=regexp
--side-by-side
Use the side by side output format.
--speed-large-files
--suppress-common-lines
Do not print common lines in side by side format.
Treat all files as text and compare them line-by-line, even if they do not appear to be text.
Use the unified output format.
--unchanged-group-format=format
Use format to output a group of common lines taken from both files in if-then-else format.  see node `Line group formats' in the CVS manual.
--unchanged-line-format=format
Use format to output a line common to both files in if-then-else format.  see node `Line formats' in the CVS manual.
--unified[=lines]
Use the unified output format, showing lines (an integer) lines of context, or three if lines is not given.  For proper operation, patch typically needs at least two lines of context.
--width=columns
Use an output width of columns in side by side format.
Line group formats Line group formats let you specify formats suitable for many applications that allow if-then-else input, including programming languages and text formatting languages.  A line group format specifies the output format for a contiguous group of similar lines.
For example, the following command compares the TeX file myfile with the original version from the repository, and outputs a merged file in which old regions are surrounded by \begin{em}-\end{em} lines, and new regions are surrounded by \begin{bf}-\end{bf} lines.
cvs diff \
--old-group-format='\begin{em} %<\end{em} ' \
--new-group-format='\begin{bf} %>\end{bf} ' \
--unchanged-group-format='%=' \
--changed-group-format='\begin{em} %<\end{em} \begin{bf} %>\end{bf} ' \
Here is a more advanced example, which outputs a diff listing with headers containing line numbers in a ``plain English'' style.
--unchanged-group-format='' \
--old-group-format='-------- %dn line%(n=1?:s) deleted at %df: %<' \
--new-group-format='-------- %dN line%(N=1?:s) added after %de: %>' \
--changed-group-format='-------- %dn line%(n=1?:s) changed at %df: %<-------- to: %>' \
To specify a line group format, use one of the options listed below.  You can specify up to four line group formats, one for each kind of line group.  You should quote format, because it typically contains shell metacharacters.
These line groups are hunks containing only lines from the first file. The default old group format is the same as the changed group format if it is specified; otherwise it is a format that outputs the line group as-is.
These line groups are hunks containing only lines from the second file. The default new group format is same as the changed group format if it is specified; otherwise it is a format that outputs the line group as- is.
These line groups are hunks containing lines from both files.  The default changed group format is the concatenation of the old and new group formats.
These line groups contain lines common to both files.  The default unchanged group format is a format that outputs the line group as-is.
stands for the lines from the first file, including the trailing newline.  Each line is formatted according to the old line format (see node `Line formats' in the CVS manual).
stands for the lines from the second file, including the trailing newline.  Each line is formatted according to the new line format.
%=
stands for the lines common to both files, including the trailing newline.  Each line is formatted according to the unchanged line format.
stands for %.
%c'C'
where C is a single character, stands for C.  C may not be a backslash or an apostrophe.  For example, %c':' stands for a colon, even inside the then-part of an if-then-else format, which a colon would normally terminate.
%c'\O'
where O is a string of 1, 2, or 3 octal digits, stands for the character with octal code O.  For example, %c'\0' stands for a null character.
where F is a printf conversion specification and n is one of the following letters, stands for n's value formatted with F.
The line number of the line just before the group in the old file.
The line number of the first line in the group in the old file; equals e + 1.
The line number of the last line in the group in the old file.
The line number of the line just after the group in the old file; equals l + 1.
The number of lines in the group in the old file; equals l - f + 1.
E, F, L, M, N
Likewise, for lines in the new file.
The printf conversion specification can be %d, %o, %x, or %X, specifying decimal, octal, lower case hexadecimal, or upper case hexadecimal output respectively.  After the % the following options can appear in sequence: a - specifying left-justification; an integer specifying the minimum field width; and a period followed by an optional integer specifying the minimum number of digits.  For example, %5dN prints the number of new lines in the group in a field of width 5 characters, using the printf format "%5d".
(A=B?T:E)
If A equals B then T else E.  A and B are each either a decimal constant or a single letter interpreted as above.  This format spec is equivalent to T if A's value equals B's; otherwise it is equivalent to E.
Line formats Line formats control how each line taken from an input file is output as part of a line group in if-then-else format.
For example, the following command outputs text with a one-column change indicator to the left of the text.  The first column of output is - for deleted lines, | for added lines, and a space for unchanged lines.  The formats contain newline characters where newlines are desired on output.
--old-line-format='-%l ' \
--new-line-format='|%l ' \
--unchanged-line-format=' %l ' \
To specify a line format, use one of the following options.  You should quote format, since it often contains shell metacharacters.
formats lines just from the first file.
formats lines just from the second file.
formats lines common to both files.
formats all lines; in effect, it sets all three above options simultaneously.
stands for the contents of the line, not counting its trailing newline (if any).  This format ignores whether the line is incomplete.
%L
stands for the contents of the line, including its trailing newline (if any).  If a line is incomplete, this format preserves its incompleteness.
where C is a single character, stands for C.  C may not be a backslash or an apostrophe.  For example, %c':' stands for a colon.
where F is a printf conversion specification, stands for the line number formatted with F.  For example, %.5dn prints the line number using the printf format "%.5d".  see node `Line group formats' in the CVS manual, for more about printf conversion specifications.
If the input contains tab characters and it is important that they line up on output, you should ensure that %l or %L in a line format is just after a tab stop (e.g. by preceding %l or %L with a tab character), or you should use the -t or --expand-tabs option.
Taken together, the line and line group formats let you specify many different formats.  For example, the following command uses a format similar to diff's normal format.  You can tailor this command to get fine control over diff's output.
--old-line-format='< %l ' \
--new-line-format='> %l ' \
--old-group-format='%df%(f=l?:,%dl)d%dE %<' \
--new-group-format='%dea%dF%(F=L?:,%dL) %>' \
--changed-group-format='%df%(f=l?:,%dl)c%dF%(F=L?:,%dL) %<— %>' \
diff examples The following line produces a Unidiff (-u flag) between revision 1.14 and 1.19 of backend.c.  Due to the -kk flag no keywords are substituted, so differences that only depend on keyword substitution are ignored.
$ cvs diff -kk -u -r 1.14 -r 1.19 backend.c
Suppose the experimental branch EXPR1 was based on a set of files tagged RELEASE_1_0.  To see what has happened on that branch, the following can be used:
$ cvs diff -r RELEASE_1_0 -r EXPR1
A command like this can be used to produce a context diff between two releases:
$ cvs diff -c -r RELEASE_1_0 -r RELEASE_1_1 > diffs
If you are maintaining ChangeLogs, a command like the following just before you commit your changes may help you write the ChangeLog entry. All local modifications that have not yet been committed will be printed.
$ cvs diff -u | less
export Export sources from CVS, similar to checkout • Synopsis: export [-flNnR] [-r rev|-D date] [-k subst] [-d dir] module...
• Changes: current directory.
This command is a variant of checkout; use it when you want a copy of the source for module without the cvs administrative directories.  For example, you might use export to prepare source for shipment off-site. This command requires that you specify a date or tag (with -D or -r), so that you can count on reproducing the source you ship to others (and thus it always prunes empty directories).
One often would like to use -kv with cvs export.  This causes any keywords to be expanded such that an import done at some other site will not lose the keyword revision information.  But be aware that doesn't handle an export containing binary files correctly.  Also be aware that after having used -kv, one can no longer use the ident command (which is part of the rcs suite—see ident(1)) which looks for keyword strings.  If you want to be able to use ident you must not use -kv.
export options These standard options are supported by export (see node `Common options' in the CVS manual, for a complete description of them):
Use the most recent revision no later than date.
If no matching revision is found, retrieve the most recent revision (instead of ignoring the file).
Do not run any checkout program.
Export directories recursively.  This is on by default.
Use revision tag.
In addition, these options (that are common to checkout and export) are also supported:
Create a directory called dir for the working files, instead of using the module name.  See `checkout options' in the CVS manual for complete details on how cvs handles this flag.
-k subst
Set keyword expansion mode (see node `Substitution modes' in the CVS manual).
Only useful together with -d dir.  See `checkout options' in the CVS manual for complete details on how cvs handles this flag.
history Show status of files and users • Synopsis:     history [-report] [-flags] [-options args] [files...]
• Requires: the file $CVSROOT/CVSROOT/history
cvs can keep a history file that tracks each use of the checkout, commit, rtag, update, and release commands.  You can use history to display this information in various formats.
Logging must be enabled by creating the file $CVSROOT/CVSROOT/history.
history uses -f, -l, -n, and -p in ways that conflict with the normal use inside cvs (see node `Common options' in the CVS manual).
history options Several options (shown above as -report)  control  what kind of report is generated:
Report on each time commit was used (i.e., each time the repository was modified).
Everything (all record types).  Equivalent to specifying -x with all record types.  Of course, -e will also include record types which are added in a future version of cvs; if you are writing a script which can only handle certain record types, you'll want to specify -x.
-m module
Report on a particular module.  (You can meaningfully use -m more than once on the command line.)
Report on checked-out modules.  This is the default report type.
Report on all tags.
-x type
Extract a particular set of record types type from the cvs history. The types are indicated by single letters, which you may specify in combination.
Certain commands have a single record type:
rtag
One of five record types may result from an update:
A merge was necessary but collisions were detected (requiring manual merging).
A merge was necessary and it succeeded.
A working file was copied from the repository.
A working file was patched to match the repository.
The working copy of a file was deleted during update (because it was gone from the repository).
One of three record types results from commit:
A file was added for the first time.
A file was modified.
A file was removed.
The options shown as -flags constrain or expand the report without requiring option arguments:
Show data for all users (the default is to show data only for the user executing history).
Show last modification only.
Show only the records for modifications done from the same working directory where history is executing.
The options shown as -options args constrain the report based on an argument:
-b str
Show data back to a record containing  the  string str  in  either the module name, the file name, or the repository path.
Show data since date.  This is slightly different from the normal use of -D date, which selects the newest revision older than date.
-f file
Show data for a particular file (you can specify several -f options on the same command line).  This is equivalent to specifying the file on the command line.
-n module
Show data for a particular module (you can specify several -n options on the same command line).
-p repository
Show data for a particular source repository  (you can specify several -p options on the same command line).
-r rev
Show records referring to revisions since the revision or tag named rev appears in individual rcs files.  Each rcs file is searched for the revision or tag.
-t tag
Show records since tag tag was last added to the history file.  This differs from the -r flag above in that it reads only the history file, not the rcs files, and is much faster.
-u name
Show records for user name.
-z timezone
Show times in the selected records using the specified time zone instead of UTC.
import Import sources into CVS, using vendor branches • Synopsis: import [-options] repository vendortag releasetag...
• Requires: Repository, source distribution directory.
Use import to incorporate an entire source distribution from an outside source (e.g., a source vendor) into your source repository directory. You can use this command both for initial creation of a repository, and for wholesale updates to the module from the outside source.  See `Tracking sources' in the CVS manual for a discussion on this subject.
The repository argument gives a directory name (or a path to a directory) under the cvs root directory for repositories; if the directory did not exist, import creates it.
When you use import for updates to source that has been modified in your source repository (since a prior import), it will notify you of any files that conflict in the two branches of development; use checkout -j to reconcile the differences, as import instructs you to do.
If cvs decides a file should be ignored (see node `cvsignore' in the CVS manual), it does not import it and prints I  followed by the filename (see node `import output' in the CVS manual for a complete description of the output).
If the file $CVSROOT/CVSROOT/cvswrappers exists, any file whose names match the specifications in that file will be treated as packages and the appropriate filtering will be performed on the file/directory before being imported.  See `Wrappers' in the CVS manual.
The outside source is saved in a first-level branch, by default 1.1.1. Updates are leaves of this branch; for example, files from the first imported collection of source will be revision 1.1.1.1, then files from the first imported update will be revision 1.1.1.2, and so on.
At least three arguments are required.  repository is needed to identify the collection of source.  vendortag is a tag for the entire branch (e.g., for 1.1.1).  You must also specify at least one releasetag to uniquely identify the files at the leaves created each time you execute import.  The releasetag should be new, not previously existing in the repository file, and uniquely identify the imported release,
Note that import does not change the directory in which you invoke it. In particular, it does not set up that directory as a cvs working directory; if you want to work with the sources import them first and then check them out into a different directory (see node `Getting the source' in the CVS manual).
import options This standard option is supported by import (see node `Common options' in the CVS manual for a complete description):
There are the following additional special options.
-b branch
See `Multiple vendor branches' in the CVS manual.
Use each file's modification time as the time of import rather than the current time.
Indicate the keyword expansion mode desired.  This setting will apply to all files created during the import, but not to any files that previously existed in the repository.  See `Substitution modes' in the CVS manual for a list of valid -k settings.
-I name
Specify file names that should be ignored during import.  You can use this option repeatedly.  To avoid ignoring any files at all (even those ignored by default), specify `-I !'.
name can be a file name pattern of the same type that you can specify in the .cvsignore file.  See `cvsignore' in the CVS manual.
-W spec
Specify file names that should be filtered during import.  You can use this option repeatedly.
spec can be a file name pattern of the same type that you can specify in the .cvswrappers file. see node `Wrappers' in the CVS manual.
import output import keeps you informed of its progress by printing a line for each file, preceded by one character indicating the status of the file:
U file
The file already exists in the repository and has not been locally modified; a new revision has been created (if necessary).
N file
The file is a new file which has been added to the repository.
The file already exists in the repository but has been locally modified; you will have to merge the changes.
I file
The file is being ignored (see node `cvsignore' in the CVS manual).
L file
The file is a symbolic link; cvs import ignores symbolic links.  People periodically suggest that this behavior should be changed, but if there is a consensus on what it should be changed to, it doesn't seem to be apparent.  (Various options in the modules file can be used to recreate symbolic links on checkout, update, etc.; see node `modules' in the CVS manual.)
import examples See `Tracking sources' in the CVS manual, and `From files' in the CVS manual.
log Print out log information for files • Synopsis: log [options] [files...]
Display log information for files.  log used to call the rcs utility rlog.  Although this is no longer true in the current sources, this history determines the format of the output and the options, which are not quite in the style of the other cvs commands.
The output includes the location of the rcs file, the head revision (the latest revision on the trunk), all symbolic names (tags) and some other things.  For each revision, the revision number, the author, the number of lines added/deleted and the log message are printed.  All times are displayed in Coordinated Universal Time (UTC).  (Other parts of cvs print times in the local timezone).
log uses -R in a way that conflicts with the normal use inside cvs (see node `Common options' in the CVS manual).
log options By default, log prints all information that is available.  All other options restrict the output.  Note that the revision selection options (-b, -d, -r, -s, and -w) have no effect, other than possibly causing a search for files in Attic directories, when used in conjunction with the options that restrict the output to only log header fields (-h, -R, and -t) unless the -S option is also specified.
Print information about the revisions on the default branch, normally the highest branch on the trunk.
-d dates
Print information about revisions with a checkin date/time in the range given by the semicolon-separated list of dates.  The date formats accepted are those accepted by the -D option to many other cvs commands (see node `Common options' in the CVS manual).  Dates can be combined into ranges as follows:
d1<d2
d2>d1
Select the revisions that were deposited between d1 and d2.
Select all revisions dated d or earlier.
d<
>d
Select all revisions dated d or later.
Select the single, latest revision dated d or earlier.
The > or < characters may be followed by = to indicate an inclusive range rather than an exclusive one.
Note that the separator is a semicolon (;).
Print only the name of the rcs file, name of the file in the working directory, head, default branch, access list, locks, symbolic names, and suffix.
Local; run only in current working directory.  (Default is to run recursively).
Do not print the list of tags for this file.  This option can be very useful when your site uses a lot of tags, so rather than "more"'ing over 3 pages of tag information, the log information is presented without tags at all.
Print the list of tags for this file. This option can be very useful when your .cvsrc file has a log -N entry as a way to get a full list of all of the tags.
Print only the name of the rcs file.
-rrevisions
Print information about revisions given in the comma-separated list revisions of revisions and ranges.  The following table explains the available range formats:
Revisions rev1 to rev2 (which must be on the same branch).
The same, but excluding rev1.
Revisions from the beginning of the branch up to and including rev.
Revisions starting with rev to the end of the branch containing rev.
Revisions starting just after rev to the end of the branch containing rev.
An argument that is a branch means all revisions on that branch.
branch1:branch2
branch1::branch2
A range of branches means all revisions on the branches in that range.
branch.
The latest revision in branch.
A bare -r with no revisions means the latest revision on the default branch, normally the trunk.  There can be no space between the -r option and its argument.
Suppress the header if no revisions are selected.
-s states
Print information about revisions whose state attributes match one of the states given in the comma-separated list states.  Individual states may be any text string, though cvs commonly only uses two states, Exp and dead.  See `admin options' in the CVS manual for more information.
Print the same as -h, plus the descriptive text.
-wlogins
Print information about revisions checked in by users with login names appearing in the comma-separated list logins.  If logins is omitted, the user's login is assumed.  There can be no space between the -w option and its argument.
log prints the intersection of the revisions selected with the options -d, -s, and -w, intersected with the union of the revisions selected by -b and -r.
log examples Contributed examples are gratefully accepted.
rdiff 'patch' format diffs between releases • rdiff [-flags] [-V vn] [-r t|-D d [-r t2|-D d2]] modules...
• Synonym: patch
Builds a Larry Wall format patch(1) file between two releases, that can be fed directly into the patch program to bring an old release up-to- date with the new release.  (This is one of the few cvs commands that operates directly from the repository, and doesn't require a prior checkout.) The diff output is sent to the standard output device.
You can specify (using the standard -r and -D options) any combination of one or two revisions or dates.  If only one revision or date is specified, the patch file reflects differences between that revision or date and the current head revisions in the rcs file.
Note that if the software release affected is contained in more than one directory, then it may be necessary to specify the -p option to the patch command when patching the old sources, so that patch is able to find the files that are located in other directories.
rdiff options These standard options are supported by rdiff (see node `Common options' in the CVS manual for a complete description of them):
Local; don't descend subdirectories.
In addition to the above, these options are available:
Use the context diff format.  This is the default format.
Create a summary change report instead of a patch.  The summary includes information about files that were changed or added between the releases.  It is sent to the standard output device.  This is useful for finding out, for example, which files have changed between two dates or revisions.
A diff of the top two revisions is sent to the standard output device. This is most useful for seeing what the last change to a file was.
Use the unidiff format for the context diffs.  Remember that old versions of the patch program can't handle the unidiff format, so if you plan to post this patch to the net you should probably not use -u.
-V vn
Expand keywords according to the rules current in rcs version vn (the expansion format changed with rcs version 5).  Note that this option is no longer accepted.  cvs will always expand keywords the way that rcs version 5 does.
rdiff examples Suppose you receive mail from foo@example.net asking for an update from release 1.2 to 1.4 of the tc compiler.  You have no such patches on hand, but with cvs that can easily be fixed with a command such as this:
$ cvs rdiff -c -r FOO1_2 -r FOO1_4 tc | \ > Mail -s 'The patches you asked for' foo@example.net
Suppose you have made release 1.3, and forked a branch called R_1_3fix for bug fixes.  R_1_3_1 corresponds to release 1.3.1, which was made some time ago.  Now, you want to see how much development has been done on the branch.  This command can be used:
$ cvs patch -s -r R_1_3_1 -r R_1_3fix module-name cvs rdiff: Diffing module-name File ChangeLog,v changed from revision 1.52.2.5 to 1.52.2.6 File foo.c,v changed from revision 1.52.2.3 to 1.52.2.4 File bar.h,v changed from revision 1.29.2.1 to 1.2
release Indicate that a Module is no longer in use • release [-d] directories...
• Requires: Working directory.
• Changes: Working directory, history log.
This command is meant to safely cancel the effect of cvs checkout. Since cvs doesn't lock files, it isn't strictly necessary to use this command.  You can always simply delete your working directory, if you like; but you risk losing changes you may have forgotten, and you leave no trace in the cvs history file (see node `history file' in the CVS manual) that you've abandoned your checkout.
Use cvs release to avoid these problems.  This command checks that no uncommitted changes are present; that you are executing it from immediately above a cvs working directory; and that the repository recorded for your files is the same as the repository defined in the module database.
If all these conditions are true, cvs release leaves a record of its execution (attesting to your intentionally abandoning your checkout) in the cvs history log.
release options The release command supports one command option:
Delete your working copy of the file if the release succeeds.  If this flag is not given your files will remain in your working directory.
WARNING:  The release command deletes all directories and files recursively.  This has the very serious side-effect that any directory created inside checked-out sources, and not added to the repository (using the add command; see node `Adding files' in the CVS manual) will be silently deleted—even if it is non-empty!
release output Before release releases your sources it will print a one-line message for any file that is not up-to-date.
P file
There exists a newer revision of this file in the repository, and you have not modified your local copy of the file (U and P mean the same thing).
The file has been added to your private copy of the sources, but has not yet been committed to the repository.  If you delete your copy of the sources this file will be lost.
The file has been removed from your private copy of the sources, but has not yet been removed from the repository, since you have not yet committed the removal.  See `commit' in the CVS manual.
The file is modified in your working directory.  There might also be a newer revision inside the repository.
? file
file is in your working directory, but does not correspond to anything in the source repository, and is not in the list of files for cvs to ignore (see the description of the -I option, and see node `cvsignore' in the CVS manual).  If you remove your working sources, this file will be lost.
release examples Release the tc directory, and delete your local working copy of the files.
$ cd ..         # You must stand immediately above the
# sources when you issue cvs release. $ cvs release -d tc You have [0] altered files in this repository. Are you sure you want to release (and delete) directory `tc': y $
remove Remove files from active use • Synopsis: remove [-flR] [files...]
The remove command is used to remove unwanted files from active use. The user normally deletes the files from the working directory prior to invocation of the remove command.  Only the working directory is updated.  Changes to the repository are not made until the commit command is run.
The remove command does not delete files from from the repository.  cvs keeps all historical data in the repository so that it is possible to reconstruct previous states of the projects under revision control.
To undo cvs remove or to resurrect files that were previously removed, see node `add' in the CVS manual.
remove options These standard options are supported by remove (see node `Common options' in the CVS manual for a complete description of them):
Local; run only in current working directory.  See `Recursive behavior' in the CVS manual.
Process directories recursively.  See `Recursive behavior' in the CVS manual.
In addition, these options are also supported:
Delete files before removing them.
Entire directory hierarchies are easily removed using -f, but take note that it is not as easy to resurrect directory hierarchies as it is to remove them.
remove examples Removing a file $ cvs remove remove.me cvs remove: file `remove.me' still in working directory cvs remove: 1 file exists; remove it first $ rm -f remove.me $ cvs remove remove.me cvs remove: scheduling `remove.me' for removal cvs remove: use 'cvs commit' to remove this file permanently
$ ls remove.it remove.it $ cvs remove -f remove.it cvs remove: scheduling `remove.it' for removal cvs remove: use 'cvs commit' to remove this file permanently
Removing entire directories $ tree -d a a |-- CVS `-- b
`-- CVS
3 directories $ cvs remove -f a cvs remove: Removing a cvs remove: Removing a/b cvs remove: scheduling `a/b/c' for removal cvs remove: use 'cvs commit' to remove this file permanently
update Bring work tree in sync with repository • update [-ACdflPpR] [-I name] [-j rev [-j rev]] [-k kflag] [-r tag|-D date] [-W spec] files...
After you've run 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 process, you can use the update command from within your working directory to reconcile your work with any revisions applied to the source repository since your last checkout or update.
update options These standard options are available with update (see node `Common options' in the CVS manual for a complete description of them):
Update directories recursively (default).  See `Recursive behavior' in the CVS manual.
Retrieve revision/tag rev.  This option is sticky, and implies -P.  See `Sticky tags' in the CVS manual, for more information on sticky tags/dates.
These special options are also available with update.