>>>>> On Tue Apr 11, Mitch writes: > 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. I think this a very good idea, in fact a co-worker and I did this very thing (actually used both a timestamp and an MD5) in a mini CVS clone that we did a few years back on Windows. It can save an incredible amount of traffic. Lee.
- Could timestamps be replaced with MD5? Mitch Davis
- Re: Could timestamps be replaced with MD5? Tobias Weingartner
- Re: Could timestamps be replaced with MD5? Lee Cantey
- Re: Could timestamps be replaced with MD5? Jonathan M. Gilligan
- Re: Could timestamps be replaced with M... Pavel Roskin
- Re: Could timestamps be replaced wi... Sean Cavanaugh
- Re: Could timestamps be replac... Mitch Davis
- Re: Could timestamps be re... Martin Roehrig
- Re: Could timestamps be replac... Gerhard den Hollander
- Re: Could timestamps be re... Mitch Davis
- Re: Could timestamps be replaced with MD5? Martin Roehrig
- Re: Could timestamps be replaced with MD5? Tony Hoyle
- Re: Could timestamps be replaced with MD5? Sean Cavanaugh
