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

Re: [PATCH] Fix --depth behavior for svn add (Re: Semantics of --depth: should define WC-depth for omitted-items?)

From: Rui, Guo <timmyguo_at_mail.ustc.edu.cn>
Date: Sun, 4 May 2008 20:05:08 +0800

On Tue, Apr 29, 2008 at 10:41:54AM -0700, David Glasser wrote:
> On Tue, Apr 29, 2008 at 2:36 AM, Rui, Guo <timmyguo_at_mail.ustc.edu.cn> wrote:
> > Take the greek tree as an example. Consider a wc with directory A at
> > immediates and revision 1. And somebody introduced items A/D/new1 and
> > A/B/E/new_tree at revision 2. When we update our wc from revision 1 to 2, we
> > will notice the skipped new item A/D/new1 but not the A/B/E/new_tree. The idea
> > is that, if we include a directory in wc (a leaf directory in wc), we should
> > be able to see what happens (piratical) to it and probably would like to. If
> > we didn't bother to include the directory in wc, we are probably not
> > interested at all.
> It sounds like what you're describing is a variant of the wc crawler
> that goes one level deeper than the ambient depth.

It's possible to handle this in a customized wc crawler, but not in a way that
simply goes one level deeper, since only depth empty/files need special
attention. Moreover, handle this in client side only may result in unnecessary
data transfer, since we only need new items (after last update) in this

Rui, Guo

To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-05-04 14:05:38 CEST

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.