(cvs.info.gz) update options
(cvs.info.gz) update output
A.19.1 update options
These standard options are available with `update' ( Common
options, 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, for more
information on sticky tags/dates.
Only useful with the `-D' or `-r' flags. If no matching revision
is found, retrieve the most recent revision (instead of ignoring
Process keywords according to KFLAG. See Keyword
substitution. 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, for more information on the `status' command.
Local; run only in current working directory. Recursive
Prune empty directories. See Moving directories.
Pipe files to the standard output.
Update directories recursively (default). Recursive
Retrieve the revisions specified by TAG or, when DATE is specified
and TAG is a branch tag, the version from the branch TAG as it
existed on DATE. This option is sticky, and implies `-P'. See
Sticky tags, for more information on sticky tags/dates.
Also see Common options.
These special options are also available with `update'.
Reset any sticky tags, dates, or `-k' options. See Sticky
tags, for more information on sticky tags/dates.
Overwrite locally modified files with clean copies from the
repository (the modified file is saved in `.#FILE.REVISION',
Create any directories that exist in the repository if they're
missing from the working directory. Normally, `update' acts only
on directories and files that were already enrolled in your
This is useful for updating directories that were created in the
repository since the initial checkout; but it has an unfortunate
side effect. If you deliberately avoided certain directories in
the repository when you created your working directory (either
through use of a module name or by listing explicitly the files
and directories you wanted on the command line), then updating
with `-d' will create those directories, which may not be what you
Ignore files whose names match NAME (in your working directory)
during the update. You can specify `-I' more than once on the
command line to specify several files to ignore. Use `-I !' to
avoid ignoring any files at all. cvsignore, for other
ways to make CVS ignore some files.
Specify file names that should be filtered during update. 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. Wrappers.
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.
Note that using a single `-j TAGNAME' option rather than `-j
BRANCHNAME' to merge changes from a branch will often not remove
files which were removed on the branch. Merging adds and
removals, for more.
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:
Branching and merging.
(cvs.info.gz) update output
automatically generated byinfo2html