[MERGE] Fix #87179 by using the short status format when the short format is used for log.

John Arbash Meinel john at arbash-meinel.com
Tue Dec 9 15:55:00 GMT 2008


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


...

>     jam> 1) Having a way to get short status is good
> 
> What are you (or others, don't hesitate to comment :) ready to
> sacrifice in terms of compatibility to add that ?
> 
>     jam> 2) Breaking compatibility is bad
> 
> Right, so you want a change that affects 'bzr log --short -v' *only*.
> 
>     jam> 3) Punning the log formatting with the extra options
>     jam> isn't great. We are already doing it, but may not want
>     jam> to continue the process.
> 
> Looks like I don't understand 'punning' in that context :-)

Right now doing "bzr log --short" is effectively:

"bzr log --use-the-short-log-formatter --no-merges"

The way the bug proposed it, "bzr log --short -v" would become:

"bzr log --use-the-short-log-formatter --no-merges --use-short-status"

So supplying "--short" effectively expands into 3 orthogonal options.

> 
>     jam> So I'm okay with your patch, but not quite enough to
>     jam> approve it. I would prefer if other people would vote in
>     jam> with how much they are concerned about compatibility,
>     jam> etc.
> 
> I don't have any sense of urgency on it, as said above, I tried
> to fix the bug to better understand the code since there are
> other related problems in that area, I have a dedicated thread
> for it in my current loom, so if won't be forgotten, but it can
> become part of a greater patch too (but this has other
> problems.).
> 
>         Vincent
> 

John
=:->

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkk+lNQACgkQJdeBCYSNAAPFVACgpsdylQIJ57UsLaDf/deCCSrV
ZIMAoKHf8yKfnasinLCXP/kIgCQH/RPL
=isvp
-----END PGP SIGNATURE-----



More information about the bazaar mailing list