update [ -A ] [ -C ] [ -d ] [ -D
rev] [ -f ] [ -I
pattern] [ -j
rev2] ] [ -k
kflag] [ -l | -R ] [ -p ] [ -P ] [ -W
Update the sandbox, merging in any changes from the repository. For example:
cvs -n -q update -AdP
can be used to do a quick status check of the current sandbox versus the head of the trunk of development.
The standard meanings of the common client options -D, -f, -k, -l, -r, and -R apply. Additional options are:
Reset sticky tags.
Replace modified files with clean copies.
Create and update new directories.
Provide filename patterns for files to ignore.
Merge in (join) changes between two revisions.
Check out files to standard output.
Prune empty directories.
Provide wrapper specification.
When using -C, CVS makes backups of modified files before copying the clean version. The backup files are named .# file.revision.
Using -D or -r results in sticky dates or tags, respectively, on the affected files (using -p along with these prevents stickiness). Use -A to reset any sticky tags or dates.
If two -j specifications are made,
the differences between them are computed and applied to the current
file. If only one is given, then the common ancestor of the sandbox
revision and the specified revision is used as a basis for computing
differences to be merged. For example, suppose a project has an
experimental branch, and important changes to the file
foo.c were introduced between ...