At 01:38 PM 28/06/2006 +0100, Malcolm Rowe wrote:
>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.
Another possibility which I don't think I've seen anyone bring up is
possibly starting the "Changelist" lines with a character that has no
predefined meaning, such as '>' or '-' or what have you.
$ svn st
? 1.2-back
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
Existing scripts may still get confused, but at least they won't treat
those as C(onflict) lines. It might be worth considering this even if in
the end a switch is used to display a listing with changelists.
Jonathan Gilbert
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Jun 28 16:49:44 2006