> +User interface
> +==============
> +
> +Affected commands:
> +
> + * checkout
> + * switch
> + * update
> +
> +The -N option becomes a synonym for --depth 1 for these commands.
> +This changes the existing -N behavior for these commands, but in
> +a trivial way (see below).
> +
> +checkout without --depth or -N behaves the same as it does today.
> +switch and update without --depth or -N behave the same way as
> +today IFF the working copy is fully depth:inf. switch and update
> +without --depth or -N will NOT change depth values (exception: a
> +missing directory specified on the command line will be pulled
> +in).
> +
> +Thus, 'checkout' is identical to 'checkout --depth inf', but
> +'switch' and 'update' are not the same as 'switch --depth inf'
> +and 'update --depth inf'. The former update entries according to
> +existing depth values, while the latter pulls in everything.
> +
> +To get started, run checkout with --depth 0 or --depth 1. If
> +additional files or directories are desired, pull them in with
> +update commands using appropriate --depth options.
Karl,
This last part only addresses adding items to a working copy, or
removing *entire subtrees*. What if I want to remove 1 file, or a
specific entry in the current dir, which also has a very complex
subdir structure in another entry? In that case 'svn up --depth 0'
followed by reconstructing the subtree(s) isn't a very user friendly
thing to do.
I think we need a UI to explicitly remove an entry from the working
copy without influencing peer entries.
(Yes, this is a UI problem, but, hey, you checked in the UI part too!)
bye,
Erik.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Jul 14 12:56:37 2006