Re: depth of the operation vs. depth of the WC

On Fri, Apr 4, 2008 at 10:42 AM, Rui, Guo <timmyguo_at_mail.ustc.edu.cn> wrote:
> > > I implemented it more for the sake of non-'svn' clients doing various
> > > operations with the reporter. I figure we can build in "exclude"
> > > capability to wc-ng. (And it would be fine to implement it in the
> > > current wc model too, similarly to "absent" directories.)
>
> What does wc-ng means? A re-design to libwc? I found a document in notes
> directories for it, but not yet read it.

Yeah, a redesign for libsvn_wc, currently in the design phases.

> > Er, and also you're right that this is pretty important for the
> > deselection interface when you're deselecting a child of something
> > that isn't depth-empty (or a directory child of something that is
> > depth-files).
>
> Maybe I'll try to bring in the depth-exclude in my deselection design if
> there is still enough time after I've done with existing depth values.
> Anyway, this is another story and is not in my plan yet. :-)

Yeah, I'm just not sure that it's good if

$ svn co $REPO/trunk
$ svn-exclude trunk/subdir

suddenly means that "svn up trunk" won't add new subdirs ever.

--dave

-- 
David Glasser | glasser@davidglasser.net | http://www.davidglasser.net/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org