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

From: Junio C Hamano <gitster@pobox.com>
Date: Oct 16, 2025, 21:18 UTC
Message-ID: <xmqqqzv21r76.fsf@gitster.g>
In-Reply-To: <7205e71da08f22db757b5dc0bcf3fef27db40ea4.camel@HansenPartnership.com>

James Bottomley <James.Bottomley@HansenPartnership.com> writes:

Show 5 quoted lines

> 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.