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

Re: Possible depth bug with status?

From: Vlad Georgescu <vgeorgescu_at_gmail.com>
Date: 2007-10-31 19:39:13 CET

Mark Phippard wrote:
> I have run into a new variant of this problem.
> I have a checked out project (depth=infinity). This project makes use
> of svn:externals.
> In JavaHL, we have a getStatus method that has an ignoreExternals
> boolean. I always run this with false to drive our Synchronize view.
> We want to show all incoming changes. This has always worked well.
> With current 1.5 code, if I pass depth=unknown to the API then it no
> longer processes the svn:externals (regardless of the setting in the
> boolean). If I change it to depth=infinity then it works properly.
> The problem of course is that if use depth=infinity but the WC is
> something different, then the command shows stuff that it shouldn't.
> So I do not think there is currently any combination of settings that
> gives me what I would want -- proper depth behavior, AND descend into
> svn:externals if they are present.

r27527 should have fixed this problem (by making status process
externals when depth is svn_depth_unknown, like the other subcommands do).

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Oct 31 19:39:29 2007

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.