David Berry writes:
>
> Thanks for your quick response. We have had
> the situation in the past where a developer
> checks out a source set, makes some really bad
> changes and then checks it back into RCS,
> soon to be CVS. We in maintenance are charged
> with the task of fixing these blunders in the
> latest revision. Suppose I check out the source
> prior to the screw up, make fixes and try to check
> it in on top of the bad version. I get up-to-date
> check failures! What am I to do?
There are lots of things you can do. You could do just as you say, and
then do ``cvs up -A'' to merge any subsequent changes with your fixed
code before you check it in. If you want to reverse an entire checkin,
you can do that by using two -j options to update (or checkout). For
example, if you wanted to undo all the changes between revision 1.23 and
1.24, you do:
cvs up -j1.24 -j1.23 file
(note the order of the -j options, that's what makes it undo the
changes).
-Larry Jones
Moms and reason are like oil and water. -- Calvin
_______________________________________________
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs
