On 1/18/2021 2:31 PM, Aiyee Bee wrote: > Hi Antonio and Derrick! > >> I think what you really want is --full-history --simplify-merges [1]. This >> will show the merges that "fork" the history into parallel tracks where >> at least two of them contain interesting commits. > > It doesn't look like the implementation of --simplify-merges helps much > here. That makes its decision on basis of the parents of the commit, which is > simple to do as it's information attached freely to each commit. I think the > problem here would be figuring out, given any commit, how many of its children > are "relevant" commits. You should definitely give this a try instead of assuming things about the implementation. The algorithm uses a lot of "simplifying" that makes it look like the decision is a local one. However, I assure you that is not the case. Please assemble a test case that demonstrates the behavior you want and how that is different from what is present in --simplify-merges. -Stolee
