[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: Bert Huijben <bert_at_vmoo.com>
Date: Tue, 17 Aug 2010 13:29:39 -0700

> -----Original Message-----
> From: Stefan Küng [mailto:tortoisesvn_at_gmail.com]
> Sent: dinsdag 17 augustus 2010 12:45
> To: Bert Huijben
> Cc: 'Subversion Development'
> Subject: Re: svn_client_status5() and depth
>
> 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
> >>
> >> Hi,
> >>
> >> * 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
> > 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?

No it doesn't change the WC, but it sends different information to the
network.
In one case the depth stored in the working copy is used (to filter the
information you miss in your example) and in the other case the information
isn't filtered.

svn status -u was designed to show what an equivalent 'svn up' would do and
in this case it didn't do that. Instead it just showed everything below,
without looking at the ambient depth.

        Bert
Received on 2010-08-17 22:30:51 CEST

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