[Bug 6334] New: In log -G show first parent of merge changeset to left of second parent

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

[Bug 6334] New: In log -G show first parent of merge changeset to left of second parent

mercurial-bugs-2
https://bz.mercurial-scm.org/show_bug.cgi?id=6334

            Bug ID: 6334
           Summary: In log -G show first parent of merge changeset to left
                    of second parent
           Product: Mercurial
           Version: stable branch
          Hardware: PC
                OS: Linux
            Status: UNCONFIRMED
          Severity: feature
          Priority: wish
         Component: Mercurial
          Assignee: [hidden email]
          Reporter: [hidden email]
                CC: [hidden email]
    Python Version: ---

Currently, when displaying a merge changeset and its ancestors using hg log -G,
Mercurial puts the parent with the lower revision number to the left of the
parent with the higher revision number, so the output looks something like
this:

@    changeset:   3:3f23f61ba894
|\   parent:      2:3af30b7d0b2a
| |  parent:      1:d8dfb1a91133
| |
| o  changeset:   2:3af30b7d0b2a
| |  parent:      0:a8e5bfe19697
| |
o |  changeset:   1:d8dfb1a91133
|/
o  changeset:   0:a8e5bfe19697

(I omitted user, date, summary and tag lines for brevity.)

This means that, regardless of whether I merge changeset 2 into changeset 1 or
vice versa, the graph that hg log -G outputs looks the same. The only way I can
tell which parent is the first parent of changeset 3 is by reading the "parent"
lines under changeset 3's info.

I think it would be less confusing if Mercurial always displayed the first
parent to the left of the second parent. So if changeset 1 were the first
parent, the graph would look like (omitting boilerplate lines):

@    changeset:   3:3f23f61ba894
|\
| o  changeset:   2:3af30b7d0b2a
| |
o |  changeset:   1:d8dfb1a91133
|/
o  changeset:   0:a8e5bfe19697

while if changeset 2 were the first parent, then the graph would look like
(again omitting boilerplate):

@    changeset:   3:3f23f61ba894
|\
o |  changeset:   2:3af30b7d0b2a
| |
| o  changeset:   1:d8dfb1a91133
|/
o  changeset:   0:a8e5bfe19697

(For comparison, that is what Git currently does.)

--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
Mercurial-devel mailing list
[hidden email]
https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel