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

Opinions on changing add/add conflict resolution?

From
Elijah Newren <newren@gmail.com>
Date
Mar 12, 2018, 18:32 UTC
Message-ID
<CABPp-BEXcvgxcn4-OrDhjUpuOsGCJwE_XT+0eYOK4Ad_O5maOg@mail.gmail.com>
Hi everyone,

I'd like to change add/add conflict resolution. Currently when such a conflict occurs (say at ${path}), git unconditionally does a two-way merge of the two files and sticks the result in the working tree at ${path}.

I would like to make it instead first check whether the two files are similar; if they are, then do the two-way merge, but if they're not, then instead write the two files out to separate paths (${path}~HEAD and ${path}~$MERGE, while making sure that ${path} is removed from the working copy).

Thoughts?

I have a patch series[1] with more details and other changes, but wanted to especially get feedback on this issue even from folks that didn't have enough time to read the patches or even the cover letter.

Thanks, Elijah

[1] https://public-inbox.org/git/20180305171125.22331-1-newren@gmail.com/
Next: Jonathan Nieder
Message 1 of 22 in “Opinions on changing add/add conflict resolution?”
  1. Elijah NewrenMar 12, 2018
  2. Jonathan NiederMar 12, 2018
  3. Elijah NewrenMar 12, 2018
  4. Jonathan NiederMar 12, 2018
  5. Hilco WijbengaMar 12, 2018
  6. Jonathan NiederMar 12, 2018
  7. Elijah NewrenMar 13, 2018
  8. Elijah NewrenMar 13, 2018
  9. Junio C HamanoMar 13, 2018
  10. Elijah NewrenMar 13, 2018
  11. Junio C HamanoMar 13, 2018
  12. Elijah NewrenMar 13, 2018
  13. Junio C HamanoMar 13, 2018
  14. Elijah NewrenMar 13, 2018
  15. Jonathan NiederMar 13, 2018
  16. Elijah NewrenMar 13, 2018
  17. Junio C HamanoMar 13, 2018
  18. Ævar Arnfjörð BjarmasonMar 12, 2018
  19. Fwd: Opinions on changing add/add conflict resolution?Elijah Newren, Mar 13, 2018
  20. Junio C HamanoMar 13, 2018
  21. Ævar Arnfjörð BjarmasonMar 13, 2018
  22. Elijah NewrenMar 13, 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.