git/list[1] front-page[2] threads[3] people[4] search[5] about
 

How to debug a "git merge"?

From
Lars Schneider <larsxschneider@gmail.com>
Date
Mar 14, 2018, 16:56 UTC
Message-ID
<7895279B-9FB6-471B-A8BA-53315B265A51@gmail.com>
Hi,

I am investigating a Git merge (a86dd40fe) in which an older version of a file won over the newer version. I try to understand why this is the case. I can reproduce the merge with the following commands: $ git checkout -b test a02fa3303 $ GIT_MERGE_VERBOSITY=5 git merge --verbose c1b82995c

The merge actually generates a merge conflict but not for my problematic file. The common ancestor of the two parents (merge base) is b91161554.

The merge graph is not pretty (the committers don't have a clean branching scheme) but I cannot spot a problem between the merge commit and the common ancestor: $ git log --graph --oneline a86dd40fe

Can you give me a hint how to debug this merge further? How can I understand why Git picked a certain version of a file in a merge?

I am using Git 2.16.2 on Linux.

Thanks, Lars

Next: Derrick Stolee
Message 1 of 8 in “How to debug a "git merge"?”
  1. Lars SchneiderMar 14, 2018
  2. Derrick StoleeMar 14, 2018
  3. Lars SchneiderMar 14, 2018
  4. Derrick StoleeMar 20, 2018
  5. Jeff KingMar 14, 2018
  6. Lars SchneiderMar 15, 2018
  7. Jeff KingMar 15, 2018
  8. Elijah NewrenMar 15, 2018

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.