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

[RFC PATCH] builtin/format-patch: print a warning for skipped merge commits?

From
Dominique Martinet <asmadeus@codewreck.org>
Date
Dec 31, 2025, 03:42 UTC
Message-ID
<20251231034217.2498648-1-asmadeus@codewreck.org>

Git format-patch historically silently ignores merge commits, because a merge commit simply cannot be fully described by a simple patch.

This can be surprising for users, especially when coupled with newer merge-heavy workflows such as encouraged by jj: trying to generate a patch from a jj commit that was a git merge with "content" will not generate anything, without any message.

This RFC patch illustrates how we could easily print a warning, but perhaps the warning would only make sense if no other commit has been formatted? I don't think it hurts all that much to print all the time but I can see it being annoying in some use-cases, so it'd likely deserve a config knob if we inconditionally print that... Also perhaps pretty-printing the merge commit a bit better like printing the subject...

Please let me know what you think would make sense here and I'll send a more proper patch (tests..) Thanks!

Reported-by: Julien Moutinho <julm@sourcephile.fr>
Signed-off-by: Dominique Martinet <asmadeus@codewreck.org>
---
 builtin/log.c | 6 +++++-
 1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/builtin/log.c b/builtin/log.c
index d4cf9c59c81a..b21274461cd3 100644
--- a/builtin/log.c
+++ b/builtin/log.c
@@ -2044,7 +2044,6 @@ int cmd_format_patch(int argc,
 	rev.expand_tabs_in_log_default = 0;
 	rev.verbose_header = 1;
 	rev.diff = 1;
-	rev.max_parents = 1;
 	rev.diffopt.flags.recursive = 1;
 	rev.diffopt.no_free = 1;
 	memset(&s_r_opt, 0, sizeof(s_r_opt));
@@ -2274,6 +2273,11 @@ int cmd_format_patch(int argc,
 		die(_("revision walk setup failed"));
 	rev.boundary = 1;
 	while ((commit = get_revision(&rev)) != NULL) {
+		if (commit->parents->next) {
+			warning(_("skipped merge commit %s"),
+				oid_to_hex(&commit->object.oid));
+			continue;
+		}
 		if (commit->object.flags & BOUNDARY) {
 			boundary_count++;
 			origin = (boundary_count == 1) ? commit : NULL;
-- 
2.52.0
Next: Junio C Hamano
Message 1 of 6 in “builtin/format-patch: print a warning for skipped merge commits?”
  1. builtin/format-patch: print a warning for skipped merge commits?Dominique Martinet, Dec 31, 2025
  2. Junio C HamanoDec 31, 2025
  3. Jeff KingJan 2, 2026
  4. Dominique MartinetJan 3, 2026
  5. Junio C HamanoJan 4, 2026
  6. Dominique MartinetFeb 1, 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.