Requires: repository, working directory.
This is the cvsnt interface to assorted administrative facilities. Some of them have questionable usefulness for cvsnt but exist for historical purposes. Some of the questionable options are likely to disappear in the future. This command does work recursively, so extreme care should be used.
Do not use this command unless you know what you are doing. Some of the admin commands can have unexpected consequences.
On unix, if there is a group named cvsadmin, only members of that group can run cvs admin. This group should exist on the server, or any system running the non-client/server cvsnt. To disallow cvs admin for all users, create a group with no users in it. On Windows, server administrators are able to use the admin command.
This option is provided as legacy support for older servers and has no function under CVSNT.
Lock the revision with number
rev. If a
branch is given, lock the latest revision on that branch. If
rev is omitted, lock the latest revision on
the default branch. There can be no space between
-l and its argument.
This command is depreciated in favour of the 'edit -c' and 'edit -x' commands, which gives pseudo and genuine reserved checkouts.
Replace the log message of revision
Deletes (outdates) the revisions
Note that this command can be quite dangerous unless you
know exactly what you are doing (for
example see the warnings below about how the
rev2 syntax is
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 cvsnt 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.
range in one of the following
Collapse all revisions between rev1 and rev2, so that cvsnt only stores the differences associated with going from rev1 to rev2, not intermediate steps. For example, after -o 1.3::1.5 one can retrieve revision 1.3, revision 1.5, or the differences to get from 1.3 to 1.5, but not the revision 1.4, or the differences between 1.3 and 1.4. Other examples: -o 1.3::1.4 and -o 1.3::1.3 have no effect, because there are no intermediate revisions to remove.
Collapse revisions between the beginning of the
rev itself. The branchpoint and
rev are left intact. For example,
-o ::188.8.131.52 deletes revision 184.108.40.206,
revision 220.127.116.11, and everything in between, but leaves
1.3 and 18.104.22.168 intact.
Collapse revisions between
and the end of the branch containing
left intact but the head revision is deleted.
Delete the revision
example, -o 1.3 is equivalent to
Delete the revisions from
rev2, inclusive, on the same branch.
One will not be able to retrieve
rev2 or any of the revisions in
between. For example, the command cvs admin
-oR_1_01:R_1_02 . is rarely useful. It means to
delete revisions up to, and including, the tag R_1_02. But
beware! If there are files that have not changed between
R_1_02 and R_1_03 the file will have the
same numerical revision number assigned to the
tags R_1_02 and R_1_03. So not only will it be impossible
to retrieve R_1_02; R_1_03 will also have to be restored
from the tapes! In most cases you want to specify
Delete revisions from the beginning of the branch
rev up to and including
Delete revisions from revision
itself, to the end of the branch containing
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 cvsnt 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 cvsnt will delete the revisions but leave the symbolic names pointing to nonexistent revisions. This behavior is preserved for compatibility with previous versions of cvsnt, but because it isn't very useful, in the future it may change to be like the :: case.
Due to the way cvsnt handles branches
rev cannot be specified symbolically if it is
a branch. the section called “Magic branch numbers”, for an
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 (the section called “Merging differences between any two revisions”).
Run quietly; do not print diagnostics.
Useful with cvsnt. Write descriptive text from the
contents of the named
file into the rcs file,
deleting the existing text. The
may not begin with -. The descriptive text
can be seen in the output from cvs log (the section called “log--Print out log information for files”). There can be no space between
-t and its argument.
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.
Similar to -t
Write descriptive text from the
the rcs file, deleting the existing text. There can be no space
between -t and its argument.