Mark new revisions since superseeded merge proposal in code review

[Mathias Gug]

In a merge proposal the comments from the superseeded merge proposal are automatically included.

A similar concept could be added to the Unmerged revisions section where new revisions since the superseeded merge proposal could be highlighted.

This would help the reviewer figuring out what has changed since the last review was done.

[Tim Penhey (thumper)]

What actual use case are you interested in following here?

We have several changes planned or in progress that are related here.

Firstly we are going to have the option to resubmit but start a new conversation. This will effectively mark start a new merge proposal with the data from the first.

Another change is incremental diffs shown on the proposal page for commits made during the conversation.

[Robert Collins (lifeless)]

I think the use case was 'figure out what has changed since the last review was done' - but I'm not entirely sure how that ties into the requested change.