On Tuesday, April 11, Mitch Davis wrote:
>
> My suggestion is, instead of storing the timestamp
> in CVS/Entries, the CVS client stores the MD5 of
> the file. And the up-to-date check performs an
> MD5 of the file. If they don't match, the CVS
> client knows beyond all doubt that the file has
> changed, and can contact the CVS server.
This has been discussed before. Personally, I think
this is a good idea. However, I believe that protocol
changes would be required in order to get this to work.
Chances are the protocol changes would be minimal, and
even somewhat backwards compatible (at least to 1.10),
so it should not be too hard to do...
--Toby.
