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, c

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 going in this release, and whether it went in the last release? > B) I need to know which change is the first change in the release branch because I'd like to start a new topic branch with that as my starting point so that I'll be as current as possible and still know that I can do a clean merge into master and release later; You need the earliest on the release branch that has not also been on the master branch. > C)I need to know where topic branch started so that I can gather all the patches up together and send them to a colleague for review. You need to send them all the commits on the topic branch that aren't merged elsewhere. git has nice syntax for specifying ranges of commits of these forms.