|
Usage: ccollab [global-options] addversions [--upload-comment <value>] <review> [<version-spec> [<version-spec> ...]]
addversions - Attaches any 2 given versions to a review
|
Option
|
Required?
|
Description
|
|
--upload-comment <value>
|
N
|
Comment used to upload files (default is "Local changes")
|
|
|
Y
|
Must be either an integer review-id, 'new', 'ask', or 'last'
|
<version-spec> [<version-spec> ...] |
N
|
Versions to be reviewed are given by <path> <version> [<previous version>], where <path> is the filename or server path of the file, <version> is the version to be reviewed, and <previous version> is an optional version that <version> should be diff'ed against. If <previous version> is not specified, the predecessor version of <version> will be used. If no <version-spec> is given on the command line, then one or more version specs will be read from stdin, one <version-spec> per line as described above. Note that arguments containing spaces must be quoted to be parsed correctly
|
Uploads specific versions of a file or files to a review. A version-spec is given by a filename followed by a version number, and optionally, a
previous version number:
file-name version-number [previous-version-number]
If no previous version number is explicity given, diffs will be generated
with the predecessor version as determined from the SCM system.
Adding versions for a single file can be done with command line arguments
given after the review number. To upload versions for multiple files, thefile and versions may be submitted on lines read from standard input. If
the path and versions are not given on the command line, the client will
expect to read them from stdin. Each line read should be in the format shown
above. Some example command lines for reading versions from stdin:
ccollab addversions 86753
ccollab addversions last < versionlist.txt
cat versionlist.txt | ccollab addversions new
When supplying the version list in the command line client editor or an input
file, the keyword 'local' can be used to denote the version corresponding to
the local version of the file. The 'local' keyword can only be used for the
first version argument, not the previous version.
Examples of specifying versions on the command line for ClearCase:
ccollab addversions new hello.c \main\mydev\6 \main\8
ccollab addversions last Main.java /main/dev/31
To compare the local version of the ClearCase file to a previous version in
an edit list or input list, use 'local' as the initial version. If the file
is checked out as '/main/CHECKEDOUT', then 'local' is equivalent to using
'/main/CHECKEDOUT' as the initial version. Otherwise 'local' would refer to
the latest version of the file. For example, if the local file hello.c is
at version '/main/9' and has predecessor '/main/8' then all of the following
lines would be equivalent:
hello.c /main/9
hello.c local
hello.c /main/9 /main/8
hello.c local /main/8
You can also reference a LATEST version, e.g.:
ccollab addversions new hello.c \main\ga_1.0\6 \main\LATEST
To upload a version with no predecessor version, use '\main\0':
ccollab addversions new hello.c \main\ga_1.0\6 \main\0
|