Re: proposal: changelist feature

On 4/17/06, Justin Erenkrantz <justin@erenkrantz.com> wrote:
> On 4/17/06, Garrett Rooney <rooneg@electricjellyfish.net> wrote:
> > I basically agree with what Justin said, although I'm not too fond of
> > putting stuff in parens after the filename like that, I do think it
>
> Oh, I agree. I just don't know quite how to better represent it given
> the constraints on status's output though. -- justin
>

Heh, that's in fact what perforce does: something like

     /some/long/path/to/foo.c - modified XXXX
     /some/other/path/to/bar.c - added XXXX

...where XXXX is the changelist name.

Of course, I absolutely hate this output, because there are no aligned
columns at all. It's really hard to read. That's why 'svn status'
shows neatly aligned status codes, and puts the variable-length path
last.

Unfortunately, adding a changelist-name to the output of 'svn status'
would mean each line would now have *two* variable-length fields. And
I guess you guys are right -- it's not worth destroying the
streaminess of the status command just to show changelist groupings.
I guess Justin's suggestion is the best we could do.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Apr 17 21:28:09 2006