-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Jim Hyslop wrote: > Hmmm... could there be an as-yet undiscovered bug in force-commits, > maybe? I'll have a look over the code to see if anything looks > suspicious.\
Turns out it wasn't a force commit. The original 1.4 was a dead revision. The problem is solved, however. I went over the history logs and the file with 4 revisions was `cvs rm'd from one directory and `cvs add'd in another, then the new file suspiciously jumped from its initial 1.1 revision to the next commit at 1.4. After some prodding, the boss that claimed that no one messed with his repository and threatened to kick posteriors if he ever discovered such activity recalled the past more clearly and shamefully owned up to thinking he could resurrect the file himself by deleting the `dead' revision metadata. He says he'll handle kicking his own posterior. :) I'll still try to come up with a patch such that this sort of corruption is noticed on the first parse rather than allowing trunk checkouts, trunk tags, and the first trunk commit to appear successful. It should be fairly simple. Thanks for all the help. Regards, Derek - -- Derek R. Price CVS Solutions Architect Get CVS support at Ximbiot <http://ximbiot.com>! v: +1 248.835.1260 f: +1 248.835.1263 <mailto:[EMAIL PROTECTED]> -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.1 (Cygwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFEXqfkLD1OTBfyMaQRAjcaAKCMcNlemsbXCt44lG5/nVdxs7pA7ACgyoOz URt0snEnWM9mCBfeiKbhqmM= =CUcZ -----END PGP SIGNATURE----- _______________________________________________ Bug-cvs mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/bug-cvs
