When reordering two commits, you get to resolve the same conflict twice #132
Description
When two commits touch the same line, and you reorder them, you obviously get a conflict. But you get to resolve it twice, one for the first and one for the other.
I don't think the second conflict is interesting, because the correct state after both commits is already known. It would be convenient to just not be asked about that one.