Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to sales@march-hare.com.
Tony Hoyle wrote: > Jonathan M. Gilligan wrote: > Such a check could help address the greatest problem I see with CVS: there > >> is no good way to check the integrity of a repository. This means that >> corruption in repositories can go undetected for years until you try to >> check out an old revision and discover that you cannot reconstruct it >> because one or more of the difftexts between the head revision and the >> target is corrupt. > > This would tend to break the ability to hand fix the rcs file. Although > it's rare for people to do that, it's a lifesaver if something does go > wrong and you have to recover. When hand-fixing the RCS file, just remove the integrity hash code. The server would need to assume that any file without the hash code is "correct" anyway, so that it would work on an repository created by an earlier version. - Brian _______________________________________________ Cvsnt mailing list Cvsnt at cvsnt.org http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt https://www.march-hare.com/cvspro/en.asp#downcvs