Explain why 'cvs admin' should only be used on the last revision of a file.

git-svn-id: svn://svn.mplayerhq.hu/mplayer/trunk@12026 b3059339-0415-0410-9bf9-f77b7e298cf2
This commit is contained in:
diego 2004-03-15 01:46:03 +00:00
parent 91f02f6ecb
commit 05621a40dc
1 changed files with 10 additions and 4 deletions

View File

@ -95,13 +95,19 @@ I. TECH SIDE:
9. Reverting broken commits 9. Reverting broken commits
In case you committed something really broken and wish to undo it completely, In case you committed something really broken and wish to undo it completely,
you can use the 'cvs admin -o' command. Assuming that 1.123 is the latest you can use the 'cvs admin -o' command, which removes entries from the
version of the file and the one you want to remove revision history of a file. For the corner case that you remove the last
revision this amounts to reverting a commit.
Assuming that 1.123 is the last revision
cvs -z3 admin -o1.123 filename cvs -z3 admin -o1.123 filename
Do NOT do this unless you really know what you are doing and the version you will remove revision 1.123, thus reverting the file back to revision 1.122.
are removing is the last version, e.g. there were no commits after yours.
ONLY use this command to delete the LAST revision of a file. Removing other
revisions will NOT undo the changes from that revision in the last revision
and leave holes in the revision history.
Contact A'rpi <arpi@thot.banki.hu> if you have technical problems with the CVS Contact A'rpi <arpi@thot.banki.hu> if you have technical problems with the CVS