From: "Kristoffer Haugsbakk" <kristofferhaugsbakk@fastmail•com>
To: "Junio C Hamano" <gitster@pobox•com>,
"James Bottomley" <James.Bottomley@hansenpartnership•com>
Cc: git@vger•kernel.org
Subject: Re: [PATCH 0/3] add a message-id header to git
Date: Thu, 16 Oct 2025 23:28:55 +0200 [thread overview]
Message-ID: <ef34b2cf-e867-44e7-8c62-682f64f2fb0a@app.fastmail.com> (raw)
In-Reply-To: <xmqqqzv21r76.fsf@gitster.g>
On Thu, Oct 16, 2025, at 23:18, Junio C Hamano wrote:
> James Bottomley <James.Bottomley@HansenPartnership•com> writes:
>
>> So this one's a bit more deliberate. If you import email and then re-
>> send as email we can't keep the same message-id; the internet RFCs
>> require us to keep message-ids unique, so git-format-patch won't output
>> the message-id. That necessarily also means that the poor man's rebase
>> you cite above will still run, but it would drop the message-id header.
>
> That is one more reason why I do not want it in the header, or "-m"
> to overwrite existing message-id trailer. If I received a patch via
> a message, applied, and forwarded it out of a commit I previously
> created from a message I earlier received from elsewhere, I would
> want the recipient of my forwarded patch message to be able to link
> the message I forward with the original message, probably in the
> mailing list archive where I took the message from in the first
> place.
X-Git-Original-Message-ID: ?
--
Kristoffer Haugsbakk
next prev parent reply other threads:[~2025-10-16 21:29 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
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 [this message]
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=ef34b2cf-e867-44e7-8c62-682f64f2fb0a@app.fastmail.com \
--to=kristofferhaugsbakk@fastmail$(echo .)com \
--cc=James.Bottomley@hansenpartnership$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=gitster@pobox$(echo .)com \
/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