Subrevisions and merges are hidden

[David D Lowe]

There is nothing to tell you when branches have been merged into other branches.

Ideally, there should be a small information box between one revision and another stating at minimum how many subrevisions were merged into the branch and who was their author. This information box could be similar in style to the status changes of bug reports.

Example: revision 73 of lp:epidermis is actually a merged subrevision from another contributor's branch. I look like an ungrateful little wretch by not mentioning this in my commit message. If Launchpad had mentioned the fact that a merged occured at that revision, I would feel a lot better.

[Jonathan Lange (jml)]

Good point.

We're doing some restructuring of the table that's rendered from, which might make this easier, but might make it harder.