I'm one of those people that don't see a problem. I don't care what branch work happened on. I care whether it was merged or not. If I'm missing something, could someone correct me? My responses would be as follows: > A) I need to know which branch ab3e2afd was committed to know whether to include it in the change control review for the upcoming release; Why? Is there more to it than you need to know whether it is go…
For example with situation C: with cherry-picking, merging and other actions done by many people - how do you tell which commits are on the topic branch but not merged? How can you tell apart from the commit message, which could've been changed?
I think that this is his biggest issue. When the graph gets complex there is no way to tell what belongs to a topic branch, to some quick bugfix branch merged both ways, etc. etc.