"Bernhard R. Link" <brlink@xxxxxxxxxx> writes:
[offtopic: weren't you already asked not to try redirecting away direct
responses to you by using M-F-T and wasting time of people who do want to
respond directly to you? Please don't.]
> As git rebase and git format-patch linearize commits,
> having the same change in different branches causes in the
> best case duplicate patches in the produced series and in the
> worst case conflicts. If there are trivial merges involved
> (i.e. merges that do not change the tree), then this patch
> will cause git to only look at one branch, thereby avoiding
> duplicates and reducing the chance of conflicts.
The patch text itself from the cursory review looks Ok (I haven't thought
things through yet, let alone applying it, though).
One issue in the proposed commit log message above is that "trivial merge"
is an established technical term that means something very different from
"resulting tree of the merge matches exactly one of the parents' tree",
and it needs to be reworded. In this case it is easy [*1*]. Drop
everything after "If there are ...", and add something like this as a
separate paragraph:
Avoid outputting duplicate patches by ignoring all other parents when
the merge result matches exactly one of the parents.
The code comment also needs to be adjusted.
Thanks.
[Footnote]
*1* It is a good habit to acquire to question yourself if you can omit "X"
altogether and just say "Y" after writing "X (i.e. Y)".
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html