On 17.08.2010 21:37, Bert Huijben wrote:
>> -----Original Message-----
>> From: Stefan Küng [mailto:tortoisesvn_at_gmail.com]
>> Sent: dinsdag 17 augustus 2010 12:28
>> To: Subversion Development
>> Subject: svn_client_status5() and depth
>> * check out a folder with depth svn_depth_empty (svn co
>> file:///d:/testrepo/trunk testwc)
>> * cd into that folder (cd testwc)
>> * run 'svn st -u -v --depth infinity'
>> In 1.6.x, I get the status for all the files under that folder that
>> exist in the repository.
>> With the latest trunk (r986453), I only get
>> 32 32 user .
>> Status against revision: 32
>> All the files in the repository are not reported back.
>> I'm relying on the behavior of the 1.6.x version in TSVN. If this change
>> was by design, why was this changed? I couldn't find anything in recent
>> discussions about this. But that could easily be because of the
>> not-very-good search feature of the mailing list archives.
>> Or is this a bug?
> Hmm.. I think I know why you see this bug and I was responsible for
> introducing it:
> 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
> * 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?
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest Interface to (Sub)Version Control
/_/ \_\ http://tortoisesvn.net
Received on 2010-08-17 21:45:36 CEST