[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

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

From: Johan Corveleyn <jcorvel_at_gmail.com>
Date: Fri, 20 Apr 2012 15:13:35 +0200

On Fri, Apr 20, 2012 at 2:57 PM, Stefan Sperling <stsp_at_elego.de> wrote:
> 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 :)


As much as I'd like to see this implemented one day, I'm not sure if
I'll have the time to tackle this. So if anyone else is interested,
that'd be very welcome :).

In the meantime I'll start writing a script to detect "working copies
in need of cleanup" (unless someone else lets me know that something
like this has been written already). Such a script might do just a
quick check and exit early if say more than 10 mismatches (or even
just 1) are found (and have a --full option to keep going). Even if
the above feature gets implemented, such a script might still be
useful for 1.7 working copies etc ...

Received on 2012-04-20 15:14:30 CEST

This is an archived mail posted to the Subversion Users mailing list.