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

[Aaron Bentley]

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

Kent Gibson wrote:
> 
> 
> 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?

Yes they are.  They are the revisions you committed or pulled.

> 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

Won't that depend on whether the range "-r2553.2.12..2553.2.13" includes
any mainline revisions?

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

iD8DBQFGiUDQ0F+nu1YWqI0RAm1YAJ9jcs0VwfW7X0g+ioZy5qr/8Ldx6QCfSiBZ
90fPHtFMad5cT1StTL6fZ5M=
=nfBc
-----END PGP SIGNATURE-----