Why does `git merge-base` prepares a hypothetical merge commit when more than 3 commits are supplied? -


when executing git merge-base b c, command calculates merge base a , m, m hypothesical merge commit of b , c. (refer: http://git-scm.com/docs/git-merge-base#_discussion)

why merge-base command behaves way? mean, thought more sensible if result merge-base of commits; didn't know behaviour , made operational accident.


now, know "sensible" behaviour mentioned achievable giving --octopus option, wondered why not default behaviour.

is there reason or use case of current default behaviour?


Comments

Popular posts from this blog

javascript - Slick Slider width recalculation -

jsf - PrimeFaces Datatable - What is f:facet actually doing? -

angular2 services - Angular 2 RC 4 Http post not firing -