git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: git@vger.kernel.org
Subject: [PATCH 0/3] add a message-id header to git
Date: Thu, 16 Oct 2025 14:57:55 -0400	[thread overview]
Message-ID: <20251016185758.21996-1-James.Bottomley@HansenPartnership.com> (raw)

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


             reply	other threads:[~2025-10-16 18:58 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-16 18:57 James Bottomley [this message]
2025-10-16 18:57 ` [PATCH 1/3] mailinfo.c: always collect the message-id James Bottomley
2025-10-16 18:57 ` [PATCH 2/3] builtin/am.c: add a message-id commit header James Bottomley
2025-10-16 22:41   ` brian m. carlson
2025-10-16 18:57 ` [PATCH 3/3] t4150-am: add a test for message-id header collection James Bottomley
2025-10-16 19:26 ` [PATCH 0/3] add a message-id header to git Kristoffer Haugsbakk
2025-10-16 20:10   ` James Bottomley
2025-10-16 20:31     ` Kristoffer Haugsbakk
2025-10-16 20:32 ` Junio C Hamano
2025-10-16 21:00   ` James Bottomley
2025-10-16 21:18     ` Junio C Hamano
2025-10-16 21:28       ` Kristoffer Haugsbakk
2025-10-16 21:50 ` Kristoffer Haugsbakk
2025-10-16 22:15   ` Junio C Hamano

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20251016185758.21996-1-James.Bottomley@HansenPartnership.com \
    --to=james.bottomley@hansenpartnership.com \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).