On Mon, Mar 12, 2018 at 10:30 PM, Junio C Hamano <gits...@pobox.com> wrote:
> While I do not think it is a bad idea to add an optional way to write the
> contents of conflicted stages out to separate files, I do not think it is a
> good idea to change what happens to add/add conflict by default.
<snip some other good arguments>
> If anything, if rename/rename behaves differently by always writing
> the result out to separate files, it is that codepath whose behaviour
> should be fixed to match how add/add conflicts are dealt with.
Cool, thanks for the context. I'm happy to go down this path, but
there is one question I'd like your opinion on: what if the
intermediate content merges have conflicts themselves? If that
question isn't clear, let me be more precise...
Let's say A is renamed to C in HEAD, and both sides modified. We thus
need to do a 3-way content merge of C from HEAD with the two A's.
Let's call the result C1. Further, let's say that B is renamed to C
in $MERGE_BRANCH, and both sides modified. Again we need a 3-way
content merge for that other C; let's call the result C2. If neither
C1 nor C2 have content conflicts, then making rename/rename(2to1) act
like add/add is easy: just do a two-way merge of C1 and C2. But what
if C1 or C2 have conflicts? Doing a two-way merge in that case could
result in nested conflict markers. Is that okay, or would we want to
continue the old behavior of writing C1 and C2 out to separate files
for that special case only?
I'm inclined to special case content conflicts in the intermediate
merges and handle them by writing out to separate files, but I was the
one who suggested sometimes using separate files for add/add
conflicts; I'm curious if perhaps my strong aversion to nested
conflicts is also off base.