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

show all merge conflicts

From
MSMichael Spiegel <michael.m.spiegel@gmail.com>
Date
Jan 27, 2017, 16:56 UTC
Message-ID
<CANwu5-o=3p8QfWo9wQvok=UZESRVtF3Uxb3nEMZVv8AvkKYYGw@mail.gmail.com>
Hi folks,

I'm trying to determine whether a merge required a conflict to resolve after the merge has occurred. The git book has some advice (https://git-scm.com/book/en/v2/Git-Tools-Advanced-Merging) to use `git show` on the merge commit or use `git log --cc -p -1`. These strategies work when the merge conflict was resolved with a change that is different from either parent. When the conflict is resolved with a change that is the same as one of the parents, then these commands are indistinguishable from a merge that did not conflict. Is it possible to distinguish between a conflict-free merge and a merge conflict that is resolved by with the changes from one the parents?

Thanks, --Michael

Next: Jeff King
Message 1 of 9 in “show all merge conflicts”
  1. Michael SpiegelJan 27, 2017
  2. Jeff KingJan 27, 2017
  3. G. Sylvie DaviesJan 28, 2017
  4. Philip OakleyJan 28, 2017
  5. Jeff KingJan 28, 2017
  6. G. Sylvie DaviesJan 29, 2017
  7. Michael J GruberFeb 27, 2017
  8. Junio C HamanoFeb 27, 2017
  9. Jeff KingFeb 27, 2017

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.