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

Re: svn_client_status5() and depth

From: C. Michael Pilato <cmpilato_at_collab.net>
Date: Tue, 17 Aug 2010 13:32:09 -0700

On 08/17/2010 12:44 PM, Stefan Küng wrote:
>> Like I said in r957917, I think we should fix this in a different way.
>> The difference is between:
>> What would you get with
>> * svn up --depth infinity
>> and
>> * svn up --set-depth infinity
>> svn status --depth infinity used to show the last variant, but shows the
>> first variant now.
>> I think we should add an option to choose between those two variants. (By
>> enabling --set-depth on 'svn status' and a similar change to
>> libsvn_client)
> But 'svn status' with a --set-depth would mean that this call could
> change the WC?
> Until now, 'svn st' didn't change the WC at all, i.e., it was a
> read-only operation. So is such a change really wanted or necessary?

Agreed. 'svn st' is a read-only operation, period. But I suspect that Bert
is saying that the --set-depth option, when applied to 'svn status -u',
would be merely a way to describe the "mode" of the -u?

If that's the case, personally I think it would be a horrendous UI decision.
 Any option that has "set" as its action-word sounds like something's about
to be changed, which is not what's really going on here.

But that said, I believe Bert's change in r957917 was a good one -- a
correct one -- perfectly in line with the interpretation of the -u option to
'svn st' altogether. So I'm interested, Stefan, in understanding why
TortoiseSVN wants the prior behavior. What's TortoiseSVN trying to tell its
users with this extra data?

C. Michael Pilato <cmpilato_at_collab.net>
CollabNet   <>   www.collab.net   <>   Distributed Development On Demand

Received on 2010-08-17 22:32:48 CEST

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.