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

svn_client_status5 and depth_as_sticky

From: Stefan Küng <tortoisesvn_at_gmail.com>
Date: Fri, 08 Jul 2011 16:57:11 +0200


svn_client_status5 has a parameter depth_as_sticky. According to the doc

If depth_as_sticky is set and depth is not svn_depth_unknown, then the
status is calculated as if depth_is_sticky was passed to an equivalent
update command.

this should report *everything* there is, even items that are excluded
in the working copy (svn_depth_exclude) if also 'update' is true and the
passed depth is svn_depth_infinity.

This used to work a while ago, but now it does not return anything that
isn't in the working copy already anymore.

I don't know when this stopped working since I don't use this feature
very often, but I'm now testing sparse working copies and so I've
noticed that it stopped working.

May I suggest to also add this option to the CL client? currently 'svn
st' does not accept a 'set-depth' or equivalent parameter.


   oo  // \\      "De Chelonian Mobile"
  (_,\/ \_/ \     TortoiseSVN
    \ \_/_\_/>    The coolest Interface to (Sub)Version Control
    /_/   \_\     http://tortoisesvn.net
Received on 2011-07-08 16:57:50 CEST

This is an archived mail posted to the Subversion Dev mailing list.