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

Re: Git is not recognizing some merge conflicts and just accepting incoming master version

From
Junio C Hamano <gitster@pobox.com>
Date
Mar 15, 2024, 22:29 UTC
Message-ID
<xmqqzfuznn7g.fsf@gitster.g>
In-Reply-To
<ebd073ef-4ba4-44df-919a-2adefb40e3e7@kdbg.org>
Johannes Sixt <j6t@kdbg.org> writes:
Show 6 quoted lines
> That's the responsibility of the person doing the merge, who at best
> understands both branches being merged.[*] It is of utmost importance
> that a merge result produced by Git is not taken without thinking. It is
> never a no-brainer.
>
> [*] That is where good commit messages shine.
I am glad that some folks appreciate what I do every day ;-)
Previous: Johannes SixtNext: Kai
Message 6 of 8 in “Git is not recognizing some merge conflicts and just accepting incoming master version”
  1. KaiMar 14, 2024
  2. Johannes SixtMar 15, 2024
  3. KaiMar 15, 2024
  4. brian m. carlsonMar 15, 2024
  5. Johannes SixtMar 15, 2024
  6. Junio C HamanoMar 15, 2024
  7. KaiMar 16, 2024
  8. Thomas GuyotMar 23, 2024

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.