Name
update
Synopsis
update
[ -A ] [ -d ] [ -Ddate
| -rrev
] [ -f ] [ -Ipattern
] [ -jrev1
[ -jrev2
] ] [ -kkflag
] [ -l | -R ] [ -p ] [ -P ] [ -Wspec
] [file
]
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 listed in Table 18-37.
Table 18-37. update options
Option |
Description |
---|---|
|
Reset sticky tags. |
|
Create and update new directories. |
|
Provide filename patterns for files to ignore. |
|
Merge in changes between two revisions. Mnemonic: join. |
|
Check out files to standard output. |
|
Prune empty directories. |
|
Provide wrapper specification. |
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 revisions 1.2.2.1 and 1.2.2.2. Once those changes have proven ...
Get Mac OS X in a Nutshell now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.