[Cvsnt] Next release features

[Brian Smith]

Jonathan M. Gilligan wrote:
> Here is another wish:
>
> I would propose that the .4 release take advantage of this extensibility to
> implement some kind of error-checking for ,v files using CRC or hash
> function. This could be accomplished via a new newphrase in the admin,
> delta, and deltatext sections of the RCS file.

That sounds reasonable. Presumable the hash could be computed when
writing the file out. But, when would the integrity be checked? During
every checkout?

> 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.

So, do you want a hash for each revision or for the file as a whole? I
am thinking that a single hash for the file would be sufficient.

Thanks,
Brian

_______________________________________________
Cvsnt mailing list
Cvsnt at cvsnt.org
http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt