Re: File modification detection?

On Sat, 2004-04-17 at 16:39, Ben Collins-Sussman wrote:
> I'm worried that the only way to prevent this is to always-stat the
> text-base (which will slow down things even further, since we're doing
> two file stats instead of one), or to record the text-base's size in our
> entries file.

The latter seems like a better solution.

> Still, though, I could imagine somebody 'moving' a file with identical
> timestamp *and* identical size on top of the working file, and still
> fooling the algorithm. So is this road even worth pursuing?

Well, on Unix, we could still fix that case by looking at the inode
number, as Andy suggests. Not sure about Windows.

> Is there some nice philosophical quip that allows us to brush off this
> whole scenario?

I'm afraid not. The best we can do is, "this situation seems pretty
unusual; if you hit it, we're sorry."

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sun Apr 18 17:44:49 2004