In article <[EMAIL PROTECTED]>, Cornellious Mann wrote:
>Is there a concept of rollback in CVS? What is the
>best practice for removing a change that is checked
>in, but is not a good change? Thanks.
The concept of rollback is flawed in the context of a truly concurrent
versioning system. By the time you decide that the change is bad,
someone may have tagged it with a release, or started a branch at
that point and so on. Rolling back would be a destructive operation
that could corrupt the structure of the repository.
Instead, what you must do is simply to undo your edits, and then
commit a new version. CVS can help you undo your edits as a reverse
merge operation. For example, if the mistaken revision is 1.18, you
can apply a reverse patch from 1.18 to 1.17 to your working copy:
cvs update -j 1.18 -j 1.17 <filename>
This will work even if 1.18 is no longer the latest version, in which
case there may be conflicts to resolve.
_______________________________________________
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs
