From: "Kristoffer Haugsbakk" <kristofferhaugsbakk@fastmail•com>
To: "James Bottomley" <James.Bottomley@hansenpartnership•com>,
git@vger•kernel.org
Subject: Re: [PATCH 0/3] add a message-id header to git
Date: Thu, 16 Oct 2025 22:31:05 +0200 [thread overview]
Message-ID: <2a77313d-a4cb-42bc-8cc3-2811869bae13@app.fastmail.com> (raw)
In-Reply-To: <5e056d3cee9453079d4251009ecd57b208285ae0.camel@HansenPartnership.com>
On Thu, Oct 16, 2025, at 22:10, James Bottomley wrote:
> On Thu, 2025-10-16 at 21:26 +0200, Kristoffer Haugsbakk wrote:
>> On Thu, Oct 16, 2025, at 20:57, James Bottomley wrote:
>> > 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/
>> >[snip]
>>
>> Related discussions: “Change-ID”:
>>
>>[snip]
>
> So this is a different beast from change-id. Change-id is used to
> track the same change across different commits in a fully git based
> workflow ... and in that workflow a message-id wouldn't exist because
> there's really no email based interaction. The reason email projects
> need the message-id is so that all of the ci type tooling we have can
> link a commit back to the email it came from (so tip bots use it to
> reply when the commit is accepted and things). In an email based
> workflow there's not really such a thing as a global change-id and so
> the two proposals are pretty orthogonal.
They are not related in the sense that they mean the same thing. They
are related in the sense that parts of the discussion is about using a
commit header to implement the idea.
Thanks
next prev parent reply other threads:[~2025-10-16 20:31 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-16 18:57 [PATCH 0/3] add a message-id header to git James Bottomley
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 [this message]
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=2a77313d-a4cb-42bc-8cc3-2811869bae13@app.fastmail.com \
--to=kristofferhaugsbakk@fastmail$(echo .)com \
--cc=James.Bottomley@hansenpartnership$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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