Max Kirillov <max@xxxxxxxxxx> writes:
> If `git diff --cc` is used with 2 or more parents, then it shows
> all hunks which have changed compared to at least 2 parents.
> Which is reasonable, because those places are likely places for
> conflicts, and it should be displayed how they were resolved.
OK.
> But, preliminary path filtering passes a path only it was changed
> compared to each parent.
That is true, but I am a bit confused by the above, especially the
word "But" that begins the sentence. Are you talking about this
comment that describes what the caller wants to do?
/* find set of paths that every parent touches */
static struct combine_diff_path *find_paths_generic(const unsigned char *sha1,
const struct sha1_array *parents, struct diff_options *opt)
When the result of a merge exactly matches one (or more) of the
parent of the merge, we do not want to show it in the combined
format, so intersect_paths() does want to find paths that are
different from all parents. Isn't that a good thing?
> So, if a hunk which has not changed compared to some of parents is
> shown if there are more changed hunks in the file, but not shown
> if it is the only change.
>
> This looks inconsistent and for some scenarios it is desirable to show
> such changes.
Hmm, that may be true. So help me see if I understand your goal by
checking if I rephrased you correctly below:
- We want to show a combined hunk when the number of parent
variants for the hunk is more than 2 (i.e. interesting octopus)
or the result does not match any of the parents (i.e. conflict
resolution of a pairwise merge). We want to drop a hunk whose
result came from only one set of parent and the other parents had
the same original that is different from the result.
- The current code filters out a path that matches one of the
parents very early. This is OK for a two-way merge. If the
result matches one of the parent's, then any hunk we might
produce by not pre-filtering would have the result that came from
one parent (i.e. the one identical to the result) and there is
only one other parent, which cannot make it an interesting
octopus by definition.
But an octopus may merge three variants and pick the result from
one of the parents as a whole. With the pre-filtering, no hunk
from such a path is shown, even when the other two variants in
"discarded" parents are not identical.
The original to refer to are two commits bf1c32bd (combine-diff:
update --cc "uninteresting hunks" logic., 2006-02-02) and fd4b1d21
(combine-diff: add safety check to --cc., 2006-02-02).
Especially, we need to pay close attention to the discussion that
germinated the current behaviour:
http://thread.gmane.org/gmane.comp.version-control.git/15486/focus=15519
I recall that the "diff --cc" before that change was not discarding
uninteresting merges sufficiently and the two commits were a
deliberate attempt to reject what your series wants to show as
uninteresting hunks.
Two suggestions.
- This is primarily for 2/4, but can we make it more clear in the
code that we do this "include more" change only on Octopus
merges? This change should not make any difference for two-way
merges and I'd prefer to avoid extra processing of finding
matching hunks and combining, only to discard the result.
- Can you run "diff --cc" with and without your patches to the
"merge from hell" commit mentioned in the original thread and see
if we show more hunks with your patches, and make sure what are
shown additionally looked really "interesting"?
Thanks.
--
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