Go to the first
section, table of contents
The available `cvs_options' (that are given to the
left of `cvs_command') are:
Specify legal CVSROOT directory. See
section Setting up the server for password authentication.
Authenticate all communication between the client and
the server. Only has an effect on the CVS client.
As of this writing, this is only implemented when using
a GSSAPI connection (see section Direct connection with GSSAPI).
Authentication prevents certain sorts of attacks
involving hijacking the active TCP connection.
Enabling authentication does not enable encryption.
In CVS 1.9.18 and older, this specified that
RCS programs are in the bindir directory.
Current versions of CVS do not run RCS
programs; for compatibility this option is accepted,
but it does nothing.
Use tempdir as the directory where temporary files are
located. Overrides the setting of the
variable and any precompiled directory. This parameter should be
specified as an absolute pathname.
Use cvs_root_directory as the root directory
pathname of the repository. Overrides the setting of
$CVSROOT environment variable. See section The Repository.
Use editor to enter revision log information. Overrides the
setting of the
environment variables. For more information, see
section Committing your changes.
Do not read the `~/.cvsrc' file. This
option is most often used because of the
non-orthogonality of the CVS option set. For
example, the `cvs log' option `-N' (turn off
display of tag names) does not have a corresponding
option to turn the display on. So if you have
`-N' in the `~/.cvsrc' entry for `log',
you may need to use `-f' to show the tag names.
Display usage information about the specified `cvs_command'
(but do not actually execute the command). If you don't specify
a command name, `cvs -H' displays overall help for
CVS, including a list of other help options.
Do not log the `cvs_command' in the command history (but execute it
anyway). See section history--Show status of files and users, for information on command history.
Do not change any files. Attempt to execute the
`cvs_command', but only to issue reports; do not remove,
update, or merge any existing files, or create any new files.
Note that CVS will not necessarily produce exactly
the same output as without `-n'. In some cases
the output will be the same, but in other cases
CVS will skip some of the processing that would
have been required to produce the exact same output.
Cause the command to be really quiet; the command will only
generate output for serious problems.
Cause the command to be somewhat quiet; informational messages,
such as reports of recursion through subdirectories, are
Make new working files read-only. Same effect
as if the
$CVSREAD environment variable is set
(see section All environment variables which affect CVS). The default is to
make working files writable, unless watches are on
(see section Mechanisms to track who is editing files).
Set a user variable (see section Expansions in administrative files).
Trace program execution; display messages showing the steps of
CVS activity. Particularly useful with `-n' to explore the
potential impact of an unfamiliar command.
Display version and copyright information for CVS.
Make new working files read-write. Overrides the
setting of the
$CVSREAD environment variable.
Files are created read-write by default, unless
set or `-r' is given.
Encrypt all communication between the client and the
server. Only has an effect on the CVS client. As
of this writing, this is only implemented when using a
GSSAPI connection (see section Direct connection with GSSAPI) or a
Kerberos connection (see section Direct connection with kerberos).
Enabling encryption implies that message traffic is
also authenticated. Encryption support is not
available by default; it must be enabled using a
special configure option, `--enable-encryption',
when you build CVS.
Set the compression level. Only has an effect on the
Go to the first, previous, next, last section, table of contents.