i thought about the next command running cleanup, if this is the only
thing you can do to solve the problem.
--- Philip Martin <philip@codematters.co.uk> 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?
>
> --
> Philip Martin
>
>
---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: dev-help@subversion.tigris.org
>
__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Jan 9 18:50:34 2003