maybe, restore the repository from backup, prior to the command run.
-or- maybe release version 3 of your software instead of version 2, what happened to version 2 can become folklore in your company -or- stop caring about the number CVS gives files and use tags to identify baselines and branches. I would not run a script on the repository unless the risk of file revision numbers starting with 3 (instead of 2) is greater than the risk of losing your files to a corrupt repository. Just curious though, why is it important to you that revisions start with 2 instead of 3? Mark --- Lukas Ruf <[EMAIL PROTECTED]> wrote: > > Dear all, > > as I posted yesterday: > Accidentaly, I set a revision to be 3.0 instead of 2.0 by issueing the > command > cvs commit -r 3.0 > > Is there any way how I can set back the revision to 2.0? > cvs commit -r 2.0 > > Produces the error: "2.0 too low..." -- as the documentation > describes. > > So, my question: > Does anybody know how I can set the revision number to be 2.0 back > from 3.0 ? -- Do I need to create a script that I must run over the > CVS repository? > > THANKS A LOT IN ADVANCE FOR ANY HELP! > Lukas > -- > Lukas Ruf Swiss Federal Institute of Technology > Office: ETZ-G61.2 Computer Engineering and > Phone: +41/1/632 7312 Networks Laboratory (TIK) > Fax: +41/1/632 1035 ETH Zentrum > PGP 2.6: ID D20BA2ED; Gloriastr. 35 > Fingerprint 6323 B9BC 9C8E 6563 B477 BADD FEA6 E6B7 CH-8092 Zurich __________________________________________________ Do You Yahoo!? Make a great connection at Yahoo! Personals. http://personals.yahoo.com _______________________________________________ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
