Re: interrupt/cleanup mechanism

>>>>> "Ben" == Ben Collins-Sussman <sussman@collab.net> writes:
    Ben>
    Ben> On Sat, 2003-11-08 at 23:39, Karl Chen wrote:
>> It's not obvious that you need to do it in ~/dir1/, instead
>> of ~/dir1/dir2/.
    Ben>
    Ben> Ah, yes. What's unexpeceted here is that the *parent*
    Ben> directory is being locked down. Yeah, we know all about
    Ben> that bug... it's issue
    Ben> #1245.
    Ben>

Okay I see. I would have thought that even if it locks the whole
tree it only does so downward-recursively, since the repository
tree could be checked out with dir2 as the root of the working
copy.

Anyway it sounds like even when this bug is fixed, which
directories are locked may not always be apparent. If so the
error message for locked directories should specify which
directory is locked, or the error message could say "run 'svn
cleanup' in root of working copy".

Or: svn cleanup could itself cleanup the entire working copy tree
(starting at root).

-- 
Karl Chen 2003-11-09 11:48
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org