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

Re: svn commit: r27958 - in trunk/subversion: include libsvn_subr

From: David Glasser <glasser_at_davidglasser.net>
Date: 2007-11-21 03:03:41 CET

On Nov 20, 2007 8:48 PM, <glasser@tigris.org> wrote:
> Author: glasser
> Date: Tue Nov 20 17:48:42 2007
> New Revision: 27958
> Log:
> Remove svn_depth_exclude from the API. It was an implementation
> detail of some of the modules which processed depth, not a
> semantically meaningful depth itself.
> Arguably, it *would* be useful to have a concept of svn_depth_exclude,
> so that you could do things like "check all of A except for A/D".
> However, we did not implement that (at least, we didn't document it if
> we did, though it may have worked by accident). Perhaps we'll add
> this back later, completely supported.

To expand on this:

I think it *would* be useful, eventually, to have an
"svn_depth_exclude" level. This would let you do the sort of thing
Perforce client specs support where you check out an entire directory
except for a few subdirectories; we only support the opposite right

However, even though we had an svn_depth_exclude value, we weren't
*really* supporting it. It was mostly just being used as an in-memory
filter in various WC functions (like the booleans I added in the last
couple of revisions now do); though the code existed to write
"excluded" values to wc entries files, parse it from --depth flags,
etc, nothing actually expected that to happen. And svn_depth_exclude
was never recognized on the repository side (ie,

Given time constraints, full support of svn_depth_exclude should
probably wait until 1.6.


David Glasser | glasser_at_davidglasser.net | http://www.davidglasser.net/
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Nov 21 03:04:28 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.