Junio C Hamano <gitster@xxxxxxxxx> wrote: > "Shawn O. Pearce" <spearce@xxxxxxxxxxx> writes: > > > I don't really like the patch to revision.c because it winds up > > showing trivial merges too. What I really want is to have the > > "--full-history" option include a merge if either of the following > > is true: > > > > a) The resulting path does not match _any_ of the parents. We > > already handle this case correctly in revision.c and correctly > > show the "evil" merge. > > > > b) The resulting path matches one of the parents but not one of > > the others. In such a case the merge should still be output if > > a 3-way read-tree would not have chosen this result by default. > > I am not sure (b) is useful in general. Merging two branches > that fix the same issue but in different ways (think: 'maint' > and 'master' have different infrastructure and a fix initially > made on 'master' was backported to 'maint', and then later > 'maint' needed to be merged to 'master' to carry forward other > fixes) is a norm, and in such cases taking the version from the > merged-to branch is almost always what happens. (b) is useful, even in the case you just described. Try doing the above backport today. Run `git log maint -- foo.c` and find the backported commit B. Now try to see if that commit is in master in foo.c with `git log master -- foo.c`. B won't appear as the merge of maint into master chose master's revision and maint's history is pruned away. Now if the backported change was logically the same but was rewritten considerably it might take you a while to figure out why a merge discarded the change B. The merge commit might actually describe why in its message, but you can't find that particular merge commit today, even with --full-history. Not without my one-line patch. Unfortunately my one-line patch causes all of the merges that the path is involved in to be output. That can be quite a lot of them. > Also it sounds to me by "if read-tree would not have chosen this > result by default" you mean this feature would not just need to > run merge-base but also recursive merge-base synthesis, and also > recreate the structural merge (aka "rename detection") there as > well. Even if (b) is useful, it sounds like a very expensive > option, and the current merge-recursive code is structured in > such a way to be easily reused for this purpose. I think you meant here that it is *not* structured in a way to be easily reused for this purpose. That code relies heavily on the index to allow it to create that synthetic merge base. Making it callable from within the revision walker would not be a small change. But as you say, running merge-recursive here would be a very expensive option. Which is why I was saying the 3-way read-tree result as that is cheaper to compute. However the read-tree result can be different from the merge-recursive result (think renames) and yet both are still "trivial" resolutions that the user was never involved in. Of course other kinds of trivial merges (where changes from the two branches are in the same file but far enough part it can be easily merged as a 3-way file merge) appear to the path limiter as though they were an evil merge, and such merges are output. So maybe having --full-history output all merges that affected that path really is the right choice. -- Shawn. - 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
