2009/9/15 Björn Steinbrink <B.Steinbrink@xxxxxx>: > Sooner or later you'll hit a merge conflict anyway, and conflict markers > aren't that hard to understand, and IMHO are easier to handle than .rej > files, as you get to edit everything in-place. When git's diff3 gets confused trying to use ancestry, the conflict markers bring completely unrelated things that belong to the history of the file and not to the patch at hand. It's not about the conflict markers but somewhat nonsensical proposed "sides" to the resolution. > Well, you likely shouldn't be using git-apply, which is plumbing, and > can't easily make use of the "index" information in git patches to do a > three-way merge instead of a "stupid" patch application. Instead use > git-am --3way to make git perform a three-way merge, leading to > conflicts instead of plain patch rejection. Um, you got your internals wrong. git-apply is what git-am uses. cheers, m -- martin.langhoff@xxxxxxxxx martin@xxxxxxxxxx -- School Server Architect - ask interesting questions - don't get distracted with shiny stuff - working code first - http://wiki.laptop.org/go/User:Martinlanghoff -- 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