Deja User wrote:
> I know the cvs way is to keep the wrong version in the history and checkin the right
>one on top. But in my case this approach I need to just remove the wrong head
>revisions as if they were never there otherwise my revision hitstory ends up being
>littered with erroneous checkings and then checkings that are fixes to those checkins.
Is there any particular problem with that? So there are some erroneous
versions in a file's history. So what? Tag them with DO_NOT_USE or
something similar. Check in early, often, broken, whatever: a version
control system exists to track history, not pristine working copies of
software.
If you're still determined for some reason, you can use the cvs admin -o
command, as in:
cvs admin -o1.3 file.txt
Note that just about any time you use the admin subcommand you're doing
something that the authors left out of cvs for a reason.
Cheers,
Laird
--
W: [EMAIL PROTECTED] / P: [EMAIL PROTECTED]
http://www.amherst.edu/~ljnelson/
Good, cheap, fast: pick two.
_______________________________________________
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs
