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

Letting tools partially resolve conflicts in a file

From
Martin von Zweigbergk <martinvonz@gmail.com>
Date
Nov 24, 2021, 16:31 UTC
Message-ID
<CANiSa6iNpm6--qHpUFYhPfSi+ounGttA8=TAsep18A-=iyoFEQ@mail.gmail.com>
Hi,

I've searched the list and not found anything about this topic, but I figured I'd ask to be sure. The question is not specific to Git, but this seems like a forum where it might have been brought up.

You could imagine having a merge tool that was specialized for some purpose and only able to resolve a particular kind of conflict. An example would be a tool that resolves conflicts in `#include` lines or `import` lines. It could be useful to have such tools run as part of a chain of merge tools, where the final merge tool is what users normally have configured (such as `meld`, or the internal "attempt merge, or leave conflict markers" tool).

Has this problem come up before?
Thanks
Next: Junio C Hamano
Message 1 of 5 in “Letting tools partially resolve conflicts in a file”
  1. Martin von ZweigbergkNov 24, 2021
  2. Junio C HamanoNov 24, 2021
  3. Martin von ZweigbergkNov 24, 2021
  4. Junio C HamanoNov 24, 2021
  5. Martin von ZweigbergkNov 24, 2021

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.