Hi! I would like to point out a very strange behavior of git merge, which led to data loss or data duplication in the conflict file generated during a diff merge. I had to merge two branches (A and B) which contained more files (e.g. http://pastebin.ca/1483691 - before splitting branches) which were affected in the following way: * The files were formatted (indented) in branch A: http://pastebin.ca/1483684 * In branch B, their contents were altered in various points, but not significantly (refactored some statements into macros): http://pastebin.ca/1483683 I checked out branch A, and I ran "git merge B", and (obviously) there was a conflict with this file. The big surprise was to see that the generated diff file looks like this: http://pastebin.ca/1483228 The problem is with the last diff in the file, where the left portion is empty, and the right portion contains code which already was marked as merged (common), right before the start of the diff. Therefore, the mark at line 127 should really have been before line 114. Is this a bug or I am missing something? Thanks, Stefan Bucur -- 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