You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by Kevin Pilch-Bisson <ke...@pilch-bisson.net> on 2003/01/09 10:42:05 UTC

Re: Problem : svn: working copy locked:

On Thu, Jan 09, 2003 at 05:37:32PM +0000, Philip Martin wrote:
> solo turn <so...@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
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~