On 11/21/2010 07:59 PM, Greg Stein wrote:
> Hey Larry!
> Good to hear from you. Been quite a while :-P
> Yes, the delay is there to deal with filesystem timestamp resolution
> issues. I don't recall the specifics of *why*, but Bad Things can
> happen if a filesystem doesn't have enough resolution.
It has to do with our timestamp-based mod detection. On systems with
insufficient granularity, it's easy (via operations done in quick
succession) to get the WC-stored last-known-unmodified timestamp to match
the timestamp of a quite-modified working file, which causes Subversion to
not notice that the file is modified.
C. Michael Pilato <cmpilato_at_collab.net>
CollabNet <> www.collab.net <> Distributed Development On Demand
Received on 2010-11-22 15:35:59 CET
This is an archived mail posted to the Subversion Dev