[MERGE] left align log output if it only contains merge revisions
Aaron Bentley
aaron.bentley at utoronto.ca
Tue Jul 3 13:50:47 BST 2007
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Kent Gibson wrote:
>
>
> Aaron Bentley wrote:
>>> Are mainline revisions somehow golden?
>> Yes they are. They are the revisions you committed or pulled.
>
>
> As are the merge revisions.
I get the impression you understand my meaning, you're just not happy
about it. Is that right?
>>> 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?
>
> Of course. The point is that you will always get mainline revisions
> in the log output UNLESS you do some pretty specific filtering with
> -r. And if there ARE mainline revisions then the patch does not apply.
So 99% of the time this patch does not apply. And the remaining 1% of
the time, its behavior will be surprising.
Aaron
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFGikYn0F+nu1YWqI0RAudoAJ9Z8W6p6cDGT/7lbwbx7i5t9WanmQCdFhAm
s/6tMEGGpZRhB7Rt7Oy8frA=
=Z+wf
-----END PGP SIGNATURE-----
More information about the bazaar
mailing list