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

Re: Problem : svn: working copy locked:

From: Kevin Pilch-Bisson <kevin_at_pilch-bisson.net>
Date: 2003-01-09 11:42:05 CET

On Thu, Jan 09, 2003 at 05:37:32PM +0000, Philip Martin wrote:
> solo turn <soloturn99@yahoo.com> writes:
> > i would consider it more user-friendly, if svn does the svn cleanup
> > itself and not bring the error to the user. or do i not see something
> > which prevents this?
> There was a long discussion last year about using a signal handler.
> The problem is getting the signal handler to interact with multiple
> threads, there was opposition to a single global handler. Solving
> that probably involves passing a svn_context_t parameter through the
> client and wc libraries.
> On Unix a SIGKILL will leave locks whatever we do, or are you
> suggesting that the *next* command should run cleanup automatically?
I remember at one time we were thinking of having the next command run cleanup
automatically, with a warning, but for now we wanted to leave it alone, to
make debugging easier, so we could catch bugs that left us in a state that
needed cleanup.

Kevin Pilch-Bisson                    http://www.pilch-bisson.net
     "Historically speaking, the presences of wheels in Unix
     has never precluded their reinvention." - Larry Wall

  • application/pgp-signature attachment: stored
Received on Thu Jan 9 18:43:46 2003

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.