On Fri, May 6, 2011 at 4:04 PM, Bert Huijben <bert_at_qqmail.nl> wrote:
>
>
>> -----Original Message-----
>> From: Paul Burba [mailto:ptburba_at_gmail.com]
>> Sent: vrijdag 6 mei 2011 21:59
>> To: C. Michael Pilato
>> Cc: dev_at_subversion.apache.org; pburba_at_apache.org;
>> commits_at_subversion.apache.org
>> Subject: Re: svn commit: r1100321 -
>> /subversion/trunk/subversion/libsvn_wc/cleanup.c
>>
>> On Fri, May 6, 2011 at 2:48 PM, C. Michael Pilato <cmpilato_at_collab.net>
>> wrote:
>> > On 05/06/2011 02:43 PM, pburba_at_apache.org wrote:
>> >> Author: pburba
>> >> Date: Fri May 6 18:43:55 2011
>> >> New Revision: 1100321
>> >>
>> >> URL: http://svn.apache.org/viewvc?rev=1100321&view=rev
>> >> Log:
>> >> Fix issue #3835
>> >>
>> >> * subversion/libsvn_wc/cleanup.c
>> >>
>> >> (cleanup_internal): If the cleanup target is locked locked indirectly via a
>> >> recursive lock on an ancestor, then recommend cleaning up the entire
>> WC.
>> >
>> > This is a minor nit, but is it possible to generate this wrapping error in
>> > the client itself? I tend to think of our "suggestive error messages" as
>> > more appropriate when generated in client, which can then use more
>> explicit
>> > terminology:
>> >
>> > Working copy locked; trying running 'svn cleanup' on the root of the
>> > working copy (%s) instead.
>>
>> Done r1100349
>
> The client itself is 'svn', not libsvn_client :)
Ugh, that's what I get for rushing before I head out the door. Will
fix tonight.
> TortoiseSVN has no such option as 'run svn cleanup'.
>
> Bert
>
>
Received on 2011-05-06 22:30:47 CEST