On Fri, 2001-10-26 at 17:22, Karl Fogel wrote:
> Heh, found this one while writing a script to test "svn log"...
>
> We have a timestamp issue, at least on my Linux 2.2.16 system. If you
> modify a file too quickly after it's checked out or updated (i.e.,
> after its entry timestamp got set), then the file's on-disk timestamp
> will not be different from the entry's, and therefore Subversion will
> not detect your local mods unless those mods also changed the file's
> size.
>
> A human probably can't modify a file that fast, but a script sure
> can (I've included one such at the end of this mail).
Can you not change the update and check out commands so that after the
last file is written out it waits for 1 unit of time (system dependent,
but probably normally 1s) before returning?
The biggest issue with doing timestamp comparisons however is that it is
normal in a development environment to move the system clock all over
the place to simulate different conditions - which screws up timestamps
and makes the whole comparisson very error prone.
To deal with this scenario there should be a configurable option to
always do a full byte-by-byte compare.
Colin.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Oct 21 14:36:46 2006