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

git rerere and diff3

From
NDNicolas Dechesne <nicolas.dechesne@linaro.org>
Date
Jun 26, 2018, 13:25 UTC
Message-ID
<CAP71WjzHffLRCDbjvF7qpexjXDMFcJkaPpEn=AtbSMCJd6QkBQ@mail.gmail.com>
hi there,

i have noticed that merge.conflictstyle has an impact on the rerere resolution. looking briefly at the source code, it seems that git tries to discard the common ancestor diff3 bits, but what I am seeing is that if i do the following then it fails:

1. from a clean rr-cache state, with merge.conflictsytle=diff3, git
merge <branch with conflict>, resolve the conflicts, then commit
2. undo the previous merge, remove merge.conflictstyle=diff3 (disable
diff3) and merge the *same* branch, then rerere won't fix the
conflicts

Is that the expected behavior? I am not familiar with git code, but browsing rerere.c makes me think that it should have worked..

Of course, if I merge the same branch without modifying merge.conflictstyle, then the merge conflicts are properly resolved by rerere.

thanks!
Next: Junio C Hamano
Message 1 of 3 in “git rerere and diff3”
  1. Nicolas DechesneJun 26, 2018
  2. Junio C HamanoJun 26, 2018
  3. Nicolas DechesneJun 26, 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.