Some of these options have questionable usefulness for cvs but exist for historical purposes. Some even make it impossible to use cvs until you undo the effect!
-A
oldfile-a
logins-b[
rev]
cvs admin -b
: to revert to the vendor's
version when using vendor branches (see Reverting local changes).
There can be no space between -b and its argument.
-c
string-e[
logins]
-I
-i
cvs add
command
(see Adding files).
-k
substcvs update
, cvs export
, or cvs
checkout
overrides this default.
-l[
rev]
This can be used in conjunction with the
rcslock.pl script in the contrib
directory of the cvs source distribution to
provide reserved checkouts (where only one user can be
editing a given file at a time). See the comments in
that file for details (and see the README file
in that directory for disclaimers about the unsupported
nature of contrib). According to comments in that
file, locking must set to strict (which is the default).
-L
-m
rev:
msg-N
name[:[
rev]]
-n
name[:[
rev]]
-o
rangeNote that this command can be quite dangerous unless you know exactly what you are doing (for example see the warnings below about how the rev1:rev2 syntax is confusing).
If you are short on disc this option might help you. But think twice before using it—there is no way short of restoring the latest backup to undo this command! If you delete different revisions than you planned, either due to carelessness or (heaven forbid) a cvs bug, there is no opportunity to correct the error before the revisions are deleted. It probably would be a good idea to experiment on a copy of the repository first.
Specify range in one of the following ways:
::
rev2::
rev::
:
rev2:
rev:
None of the revisions to be deleted may have branches or locks.
If any of the revisions to be deleted have symbolic
names, and one specifies one of the :: syntaxes,
then cvs will give an error and not delete any
revisions. If you really want to delete both the
symbolic names and the revisions, first delete the
symbolic names with cvs tag -d
, then run
cvs admin -o
. If one specifies the
non-:: syntaxes, then cvs will delete the
revisions but leave the symbolic names pointing to
nonexistent revisions. This behavior is preserved for
compatibility with previous versions of cvs, but
because it isn't very useful, in the future it may
change to be like the :: case.
Due to the way cvs handles branches rev cannot be specified symbolically if it is a branch. See Magic branch numbers, for an explanation.
Make sure that no-one has checked out a copy of the
revision you outdate. Strange things will happen if he
starts to edit it and tries to check it back in. For
this reason, this option is not a good way to take back
a bogus commit; commit a new revision undoing the bogus
change instead (see Merging two revisions).
-q
-s
state[:
rev]
dead
state for its own purposes (see Attic); to
take a file to or from the dead
state use
commands like cvs remove
and cvs add
(see Adding and removing), not cvs admin -s
.
-t[
file]
If file is omitted,
obtain the text from standard input, terminated by
end-of-file or by a line containing . by itself.
Prompt for the text if interaction is possible; see
-I.
-t-
string-U
-u[
rev]
commit
notification (see Getting Notified).
There can be no space between -u and its argument.
-V
n-x
suffixes