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

Re: Should commit take --depth?

From: Daniel Rall <dlr_at_collab.net>
Date: 2007-07-02 22:34:28 CEST

On Sun, 01 Jul 2007, Justin Erenkrantz wrote:

> On 7/1/07, Karl Fogel <kfogel@red-bean.com> wrote:
> >Let's consider what full --depth behavior might look like for commits:
> >
> > --depth=empty: Like today's -N.
> >
> > --depth=files: Like depth=empty, plus also commits any modified
> > files directly inside a named directory target.
> >
> > --depth=immediates: Like depth=files, plus commits propchanges on
> > any subdirectories of a named directory target.
> >
> > --depth=infinity: Full recursion, the default.
> >
> >Now the $64,000 question: are depth=files and depth=immediates really
> >useful? I can see use cases for depth=empty and depth=infinity, but
> >what would we really gain by supporting the other two?
> I think, at a minimum, --depth=files should be supported via commit.
> Ambivalent, or rather non-creative enough to find a use a case for
> immediates, but probably would err on the side of including it for
> symmetry if update/status/etc support it. -- justin

I feel the same way as Justin on this one, and had the same fears of
inconsistency as voiced by Greg Hudson.

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Jul 2 22:34:20 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.