I found a file in our (Yahoo's) CVS repository today that had been truncated half-way through the revisions. The head of the file, and all of the recent revisions, are in tact so this only turns up when retrieving an older revision or trying to run 'cvs log' on the file. Naturally, all of my backups of the repository going back two months have this same problem in them (I gave up trying after that). The annoying thing is that I had no idea that this file was corrupt--if I'd been notified when it was truncated, I could have rectified the situation right away. It seems that it would be straightforward for a utility to periodically go over the files in a CVS repository and verify that they are well formed RCS files, and maybe even verify that the revisions in the RCS history apply cleanly and that RCS could produce the 1.1 version of a file, if it was called on to do so. Before I dash off and throw such a utility together, I figured it'd be worthwhile asking if anyone knows of such a thing. I don't see anything obvious in the contrib/ dir, and didn't see anything on the cvshome.org web site. Thanks, Jason
