On Thu, 6 Sep 2007, Karl Fogel wrote:
> Issue #2843 is about fact that there's no way to get rid of stuff
> after you've pulled it into a (maybe mixed-depth) working copy.
>
> For example:
>
> $ svn co --depth=empty greek-tree
> $ cd greek-tree
> $ svn up A
> [...pulls in all of A/, recursively...]
> $ vi A/D/gamma
> $ vi A/D/G/tau
> $ vi A/D/H/omega
> $ svn commit -m "Okay, done with A/ now."
> $ svn how-do-I-get-rid-of-subdir-A-now-that-I'm-done-with-it?
>
> It seems reasonable that one might want to get rid of a subdir, or at
> least "fold it up" to be empty, after one were done working with it.
> Either behavior would probably require a new subcommand, though. We
> can't just make 'svn update --depth=empty SUBDIR' fold up SUBDIR, for
> example, because 'svn update --depth=empty' already means "update the
> things you can reach with depth=empty, and touch nothing else".
>
> But I'm loathe to add a new subcommand for a feature we're not
> positive people will really need, and for which we have no real-world
> experience. So I think we should defer issue #2843 until 1.6. That
> will give the sparse-directories feature some time in the wild, and
> then we can see if a new subcommand is really needed -- or if nothing
> is needed, or if clever workarounds are available, or if someone
> thinks up another solution entirely.
>
> Thoughts?
What I do now to get rid of a subdir is:
svn update -r 0 subdir
What if that would also mark 'subdir' as excluded?
Martin
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Sep 7 12:24:44 2007