On Wed, Jan 07, 2004 at 01:35:20PM -0500, Schoep, Grant @ STORM wrote: > I just accidently checked a number of files in that I did not want to. > > I know I could just get the old version, and check that in overtop of the > incorrect one.
That's the approach that's usually recommended. (The easy way to "get the old version" is: cvs update -j<wrong-version> -j<previous-version> file Note that the higher-numbered revision is named *first*.) > But I really would like to just undo it, as the cvs log > descriptions on these files is screwed up. "cvs admin -o<rev> file" will delete revision <rev>, but that's frowned on. The intent of a revision history is to be append-only. Besides that philosophical problem, it seems to me that odd things might happen if one deletes revisions from a repository that's actually shared (I've done it on my own private repo's without any problems; just remember to do "cvs update" right afterward, since if you delete the revision that your sandbox is updated to, "cvs admin -o" does *not* fix up your sandbox). But if the bad revisions' content is ok, and it's just the log messages you're concerned about, your best bet is to use: cvs admin -m<rev>:<newmsg> file to fix the messages. > I'd rather not go in a manually muck with the ,v file in the repository. No kidding! -- | | /\ |-_|/ > Eric Siegerman, Toronto, Ont. [EMAIL PROTECTED] | | / It must be said that they would have sounded better if the singer wouldn't throw his fellow band members to the ground and toss the drum kit around during songs. - Patrick Lenneau _______________________________________________ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs