Re: Could timestamps be replaced with MD5?

[Pavel Roskin]

Hello, Tobias!

> Timestamps should be checked first.  If they mis-match, then MD5.  I'd
> say this should be enough of an "optimization" to keep *most* MD5
> computations within check.  Oh, and if the timestamp is the same, but
> the file has changed (not firing the MD5 check), a quick "touch" of the
> file should fix all...

Make no mistake! Don't touch the file! Adjust the timestamp in
CVS/Entries.

Touching the file may cause major problems, especially when it's touched
"backwards".

Pavel Roskin