I haven't tried the suggestion below but seems like a good idea, and could be added to our SF FAQ... --Guido ----- Original Message ----- From: "Mitchell Morris" <mmorris@ODYSSEY-TECHNOLOGY.COM> To: <guido@beopen.com> Sent: Wednesday, July 19, 2000 3:52 PM Subject: CVS commit backout trivia

I was reading through the python-dev archives today and saw a message from you dated 2000-07-10 about backing out a CVS commit with "cvs admin -o" and wanted to point out that there is a more history-friendly mechanism: "cvs update -j<last-bad-version> -j<last-good-version> filename". The update command will apply the diffs between <last-bad> and <last-good> in reverse order. That way you don't branch or set sticky tags that have to be cleaned up after.

hoping-this-is-of-some-miniscule-help-ly y'rs +Mitchell