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

Re: Behavior of svn remove on sparse directory.

From: David Glasser <glasser_at_davidglasser.net>
Date: Mon, 14 Jul 2008 17:30:13 -0700

On Mon, Jul 14, 2008 at 7:13 AM, C. Michael Pilato <cmpilato_at_collab.net> wrote:
> That said, I mostly agree that disallowing 'svn rm' might be a step too far
> in the conservative direction (though I'm not fully convinced of it). So
> would there be any value to having the Book and 'svn rm's' usage message
> pointing out that you should be careful when using it on a directory that is
> sparsely populated? Or how about a status indication that denotes sparsely
> populated subtrees (depth!=infinity)?

I think that would be a good idea, since currently there's no nice
(recursive) way to find out "what stuff in my working copy isn't
depth=infinity", but if it's in "svn status", it should require some
extra --show-shallow flag to display. Otherwise we're replicating the
ugliness of externals where a perfectly normal part of your long-term
wc setup shows up in every single 'svn status' forever.

--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
Received on 2008-07-15 02:30:42 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.