> >>>Conclusion: We're currently broken for use on FAT.
> >>>
> >>How does this effect use in the real world? My guess is the failure is due to the
> >>automated test: update/sleep/check, which wouldn't happen in the real world.
> >>
>
> > Subversion uses a changed-detection heuristic based heavily on the
> > timestamp of the file. To be able to detect changes made to files
> > immediately after the client exits , it waits a second after some
> > operation, hoping that enough time has passed so the changes lead to
> > a new timestamp. On FAT this won't work, because the second is too
> > short: it has a 2sec resolution.
> >
>
> That didn't answer my question. I am wondering what the chances are of this
> issued impacting normal usage, where "normal" is a person doing everything
> interactively, not a script that simulates things happing faster than is humanly
> possible.
I'd say there's no impact in the interactive scenario.
bye,
Erik.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sun Jun 26 20:13:40 2005