Greg writes:
The problem is that now I want that locally modified revision to be
committed, and in fact no longer need/want any of the changes done for
the current committed revision (1.99.2.5). So basically I want the
locally modified 1.99.2.2 to become 1.99.2.6, with none of the additions
of 1.99.2.3 - 1.99.2.5 merged (or to delete 1.99.2.3-5, and make the
locally modified 1.99.2.2 the new 1.99.2.3). I hope that makes sense...
The right way to have done that would have been to check out the tip of
the branch (1.99.2.5), used update to remove the unwanted changes ("cvs
up -j 1.99.2.5 -j 1.99.2.2 file"), make your changes, and then commit.
Since you didn't do that, the most expedient thing to do is to
temporarily rename your version of the file to something else, use "cvs
update -r branch file" to get the most recent version of the file on the
branch, replace that with your save version, then commit.
-Larry Jones
I don't NEED to compromise my principles, because they don't have
the slightest bearing on what happens to me anyway. -- Calvin