Global options CVS commands admin
This section describes the `command_options
' that
are available across several CVS commands. These
options are always given to the right of
`cvs_command
'. Not all
commands support all of these options; each option is
only supported for commands where it makes sense.
However, when a command has one of these options you
can almost always count on the same behavior of the
option as in other commands. (Other command options,
which are listed with the individual commands, may have
different behavior from one CVS command to the other).
Warning: the `history
' command is an exception; it supports
many options that conflict even with these standard options.
-D date_spec
|
Use the most recent revision no later than date_spec. date_spec is a single argument, a date description specifying a date in the past.
The specification is sticky when you use it to make a
private copy of a source file; that is, when you get a working
file using `
` A wide variety of date formats are supported by CVS. The most standard ones are ISO8601 (from the International Standards Organization) and the Internet e-mail standard (specified in RFC822 as amended by RFC1123). ISO8601 dates have many variants but a few examples are:
For more details about ISO8601 dates, see:
In addition to the dates allowed in Internet e-mail itself, CVS also allows some of the fields to be omitted. For example:
The date is interpreted as being in the local timezone, unless a specific timezone is specified. These two date formats are preferred. However, CVS currently accepts a wide variety of other date formats. They are intentionally not documented here in any detail, and future versions of CVS might not accept all of them.
One such format is
Remember to quote the argument to the `
|
-f
|
When you specify a particular date or tag to CVS commands, they
normally ignore files that do not contain the tag (or did not
exist prior to the date) that you specified. Use the `
`
Warning: The |
-k kflag
|
Alter the default processing of keywords.
See Keyword substitution, for the meaning of
kflag. Your kflag specification is
sticky when you use it to create a private copy
of a source file; that is, when you use this option
with the
The ` |
-l
|
Local; run only in current working directory, rather than recursing through subdirectories.
Warning: this is not the same
as the overall `
Available with the following commands: |
-m message
|
Use message as log information, instead of invoking an editor.
Available with the following commands: |
-n
|
Do not run any checkout/commit/tag program. (A program can be specified to run on each of these activities, in the modules database (see modules); this option bypasses it).
Warning: this is not the same as the overall `
Available with the |
-P
|
Prune empty directories. See Removing directories. |
-p
|
Pipe the files retrieved from the repository to standard output,
rather than writing them in the current directory. Available
with the |
-R
|
Process directories recursively. This is on by default.
Available with the following commands: |
-r tag
|
Use the revision specified by the tag argument instead of the
default head revision. As well as arbitrary tags defined
with the
The tag specification is sticky when you use this
with
Specifying the `
Warning: this is not the same as the overall `
` |
-W
|
Specify file names that should be filtered. You can
use this option repeatedly. The spec can be a file
name pattern of the same type that you can specify in
the ` |