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

Re: [PATCH v2] merge-file: honor merge.conflictStyle outside of a repository

From
Yannik Tausch <dev@ytausch.de>
Date
Feb 7, 2026, 21:28 UTC
Message-ID
<75AA7DD7-F8D8-48DC-ADA0-74E56CFF351D@ytausch.de>
In-Reply-To
<xmqqqzqxczeb.fsf@gitster.g>
Show 29 quoted lines
> Junio C Hamano <gitster@pobox.com> wrote:
> 
> Please do not send patches this way.  Giving responses to review
> comments is very good and strongly encouraged, but stop the response
> message with "a new version of the patch coming!" and have a separate
> message for the patch itself.
> 
> It sometimes is done to interject a sample patch in the middle of a
> discussion, but then the convention is
> 
> ... continuation of an existing discussion ...
> 
> So, how about doing things this way?
> 
> --- >8 ---
> Subject: the title of the patch
> 
> The proposed log message for the commit comes here
> 
> Signed-off-by: you
> ---
> 
> ... notes, diffstat, diff ...
> 
> i.e., use a scissors line to tell the receiving end that the rest of
> the message is a patch message, and override the Subject: with an
> in-body header.  Omit the (From <object-name> Mon Sep 17 2001)
> "magic" line, "From:" and "Date:".  The last two can be taken from
> the e-mail message anyway.
Thanks for your feedback on the patch submission format. Resending v2 as a separate message.
Previous: Junio C HamanoNext: Yannik Tausch
Message 8 of 12 in “[DOC] merge-file: document that merge.conflictStyle requires a repository”
  1. Yannik TauschFeb 5, 2026
  2. Junio C HamanoFeb 5, 2026
  3. merge-file: honor merge.conflictStyle outside of a repositoryYannik Tausch, Feb 5, 2026
  4. Junio C HamanoFeb 5, 2026
  5. Kristoffer HaugsbakkFeb 5, 2026
  6. Yannik TauschFeb 5, 2026
  7. Junio C HamanoFeb 6, 2026
  8. Yannik TauschFeb 7, 2026
  9. merge-file: honor merge.conflictStyle outside of a repositoryYannik Tausch, Feb 7, 2026
  10. Kristoffer HaugsbakkFeb 7, 2026
  11. Patrick SteinhardtFeb 9, 2026
  12. Junio C HamanoFeb 9, 2026

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.