git - Octopus merge: cosmetic, or indispensible in some cases? -
i can octopus merge of branches a
, b
head
. or, can ordinary merge of a
, followed ordinary merge of b
, , if there no conflicts end same content. use of octopus matter of taste in how commit history look, or there conflicts more resolved via octopus?
is use of octopus matter of taste in how commit history look
no. 2 sources in case isn't sample: imagine 10-20-30 branches, must merge mainline, , calculate amount of merges. single advantage of om - can merge amount of sources in 1 operation
are there conflicts more resolved via octopus?
octopus merge merge non-conflicting sources, lot of branches guaranteed disjoint changes ususal case real-world
Comments
Post a Comment