[MERGE] left align log output if it only contains merge revisions

Kent Gibson warthog618 at gmail.com
Mon Jul 2 15:50:41 BST 2007


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



Aaron Bentley wrote:
> Ian Clatworthy wrote:
>> Kent Gibson wrote:
>>> Aaron Bentley wrote:
>>>> Aaron Bentley has voted -0. Status is now: Waiting Comment: I
>>>> think merge revisions should look different from mainline
>>>> revisions, even if there are no mainline revisions.
>>> And so they do - they have '.'s in the revno ;-).
>> Aaron,
>
>> Any further input on this one? FWIW, it looks a minor change to
>> me
> that
>> I'm OK with accepting.
>
> I think it introduces a needless inconsistency.
>
How is indenting the left most revision in the log set to the left
margin inconsistent?
Are mainline revisions somehow golden?

The only time this indent patch will apply is when you explicitly
request a set of merge revisions using bzr log -rA..B, so you are
pretty well aware already of what  you will be getting.

e.g. bzr log -r2553.2.12..2553.2.13

Of course being able to do that requires the patch for 4663 - which is
also bit rotting in the review queue (thanks again to Aaron for
reviewing that one).

Cheers,
Kent.

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

iD8DBQFGiRDAgoxTFTi1P8QRAmNXAKDb7eC33ChYTd680z70fv9VfIql9ACfeGlV
yF2SpRBaZmf1ZL5g0jdJ2+Q=
=CtZ4
-----END PGP SIGNATURE-----



More information about the bazaar mailing list