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

Git merge commit message issue

From
Andrey Hsiao <andreyhsiao@gmail.com>
Date
Jul 6, 2015, 15:41 UTC
Message-ID
<loom.20150706T173729-880@post.gmane.org>
Dear list:

In the past, when we do the merge in git, if conflicts occurred, when we commit, the conflict list will be appended to the default commit message automatically.

eg: Conflicts: ....a.java ....b.java

Today, after using Git 2.3.0 for a merge, it seems now the conflict list
 was commented out by default.

I just searched a bit in the release notes, don't know whether below item has to do with this change.

---- "git interpret-trailers" learned to properly handle the "Conflicts:" block at the end. ----

We quite rely on the default generated conflict list to reminder us about the "history".

Is this the default behavior now (conflict list commented out)?

Thanks Best Regards

Next: Matthieu Moy
Message 1 of 4 in “Git merge commit message issue”
  1. Andrey HsiaoJul 6, 2015
  2. Matthieu MoyJul 6, 2015
  3. Andrey HsiaoJul 6, 2015
  4. Matthieu MoyJul 6, 2015

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.