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

Re: [PROPOSAL] Incomplete working copies (issue #695)

From: Erik Huelsmann <ehuels_at_gmail.com>
Date: 2006-06-23 20:46:19 CEST

On 6/23/06, Garrett Rooney <rooneg@electricjellyfish.net> wrote:
> On 6/23/06, Eric Gillespie <epg@pretzelnet.org> wrote:
> > "Garrett Rooney" <rooneg@electricjellyfish.net> writes:
> >
> > > One thing I don't see here is a way to remove existing files or
> > > directories. If I have a depth 0 checkout (i.e. an empty directory) I
> > > can pull in extra subdirectories via 'svn up', but how can I get rid
> > > of them if they're already there?
> >
> > I covered this with the 'svn up --depth 0 Awc/D' example. But,
> > now that i think about it, this might not be enough.
> >
> > If you have a depth 0 working copy foo containing a file bar you
> > want to get rid of, then 'svn up --depth 0 bar' works naturally.
> > But what if foo is depth 1? It would just bring bar back on the
> > next update. I guess setting a file's depth to 0 means setting
> > its parent's depth to 0, but this may be unexpected.
>
> Yeah, it really seems like what we want is a way to mark a particular
> entry as unwanted, so that it'll never get updated, even if the
> parent's depth is not 0.

Ben Reser sent a proposal for this to the list before, in a slightly
different form. I think his proposal doesn't have this problem. (See
http://svn.haxx.se/dev/archive-2005-07/0398.shtml)

Has his proposal (and work to implement it) been rejected in
preparation of this proposal? (If so, on what grounds?) Or maybe it
was just forgotten?

Just out of interest...

bye,

Erik.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Jun 23 20:47:03 2006

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.