"Derek R. Price" <[EMAIL PROTECTED]> writes:
> That shouldn't cause the problem. A standard update uses the revision and
> not the date to compute the diff. All the date comparisons going on should
> be on the client against records of dates it set in the first place.
And *that* causes a problem of its own in another circumstance. While
playing with vss2cvs, I found that (on WinNT) if you do a commit,
modify a file, then do another commit within 1 second, the commit will
do nothing since CVS believes that the file is unmodified.
I don't know if there's any practical way to get around this, other
than forcing the commit with -f (that's what I did).
_______________________________________________
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs
