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

[PATCH 0/3] add a message-id header to git

From
James Bottomley <james.bottomley@hansenpartnership.com>
Date
Oct 16, 2025, 18:57 UTC
Message-ID
<20251016185758.21996-1-James.Bottomley@HansenPartnership.com>

There has been some debate in the kernel community about how to link commits back to email, which is the basis of a lot of scripting we do

https://lore.kernel.org/ksummit/a7878386f3546ba475cdf7250ab4f5a6af2a1676.camel@HansenPartnership.com/

However, this problem is one that goes beyond the kernel, so having git always track the message-id of the email used to create the commit will be useful beyond our tools as well. The design of this message-id header is that it never shows up except in --pretty=raw output, so it will never be ordinarily visible, but can be extracted by scripts. Some projects use the -m flag of git-am to add the Message-Id to the trailers and for backwards compatibility, this functionality is not changed although it is hoped that it is now redundant.

Regards,
James
---
James Bottomley (3):
  mailinfo.c: always collect the message-id
  builtin/am.c: add a message-id commit header
  t4150-am: add a test for message-id header collection
 builtin/am.c  | 15 ++++++++++++++-
 mailinfo.c    |  5 ++---
 t/t4150-am.sh | 20 +++++++++++++++++++-
 3 files changed, 35 insertions(+), 5 deletions(-)
-- 
2.51.0
Next: James Bottomley
Message 1 of 14 in “add a message-id header to git”
  1. 0/3 add a message-id header to gitJames Bottomley, Oct 16, 2025
  2. 1/3 mailinfo.c: always collect the message-idJames Bottomley, Oct 16, 2025
  3. 2/3 builtin/am.c: add a message-id commit headerJames Bottomley, Oct 16, 2025
  4. brian m. carlsonOct 16, 2025
  5. 3/3 t4150-am: add a test for message-id header collectionJames Bottomley, Oct 16, 2025
  6. Kristoffer HaugsbakkOct 16, 2025
  7. James BottomleyOct 16, 2025
  8. Kristoffer HaugsbakkOct 16, 2025
  9. Junio C HamanoOct 16, 2025
  10. James BottomleyOct 16, 2025
  11. Junio C HamanoOct 16, 2025
  12. Kristoffer HaugsbakkOct 16, 2025
  13. Kristoffer HaugsbakkOct 16, 2025
  14. Junio C HamanoOct 16, 2025

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.