Re: script to detect timestamp-mismatches (inefficiency) in (1.7) working copies?

On Fri, Apr 20, 2012 at 02:38:19PM +0200, Stefan Sperling wrote:
> On Fri, Apr 20, 2012 at 01:16:24PM +0100, Philip Martin wrote:
> > Note that when status acquires the lock it has to repeat the timestamp
> > check, it cannot be assumed that the timestamp is still broken, or that
> > the file still exists, or that it is still a file, etc.
>
> Yes, that's why I said the timestamp would need to be checked again.
> Of course, node kind etc. would need to be verified again as well.

Filed this idea as http://subversion.tigris.org/issues/show_bug.cgi?id=4162
Let's see if somebody wants to tackle it :)
Received on 2012-04-20 14:58:26 CEST