On Tue, Jun 27, 2006 at 09:52:00AM -0700, sussman@tigris.org wrote:
> +B. Viewing changelists
> +
> +'svn status' currently shows changelist definitions by crawling the
> +working copy. Output is much more readable than perforce, because
> +we're still preserving column alignment:
> +
> +$ svn st
> +? 1.2-backports.txt
> +M notes/wc-improvements
> +
> +Changelist 'status-cleanup':
> +M subversion/svn/main.c
> + subversion/svn/revert-cmd.c
> +M subversion/svn/info-cmd.c
> +
> +Changelist 'status-printing':
> +M subversion/svn/status-cmd.c
> +
Isn't this a significant change to our existing output? Anyone who has
a script to look for Conflicted entries, for example, will now see the
changelist headers as conflicting.
I thought we'd discussed adding a switch to show changelist membership
for status?
> +### Open UI question:
> +
> + If one's CWD is deep within a working copy, how should
> +
> + $ svn subcommand --changlist mychange
> +
> + ...behave? Should it operate on *all* members of the changelist,
> + or only those members within the CWD (and recursively "below")?
> +
I'm not keen on the idea of traversing back to a 'working copy root',
though I know we use this concept in one or two places. Is there
a compelling reason not to follow the pattern that the rest of the
application uses (of operating only on the subtree below the selected
target).
Regards,
Malcolm
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Jun 28 14:39:34 2006