Re: [PATCH] headers: Preserve 'change-id' header in rebase / cherry-pick.

From: Junio C Hamano <gitster@pobox.com>
Date: Apr 7, 2026, 04:09 UTC
Message-ID: <xmqqqzor76nh.fsf@gitster.g>
In-Reply-To: <CAH7WC73-4p0RrqKNSh2G-xfpfO7QHZiXHbU_UFRkM3Q=bMWTDw@mail.gmail.com>

Matt Stark <msta@google.com> writes:

> In the discussions on
> https://lore.kernel.org/git/Z_OGMb-1oV0Ex05e@pks.im/T/#m038be849b9b4020c16c562d810cf77bad91a2c87,
> it seems to be that:
> * There is consensus that a `change-id` header provides good value

I doubt it.

There are multiple people who wanted it, but as far as I can recall, I did not get the sense that they had the same semantics in mind.

> * There is not consenus on what precise format that should take

Format is one thing, but what it means is much more important. When is it inherited? What happens when you split a single commit into three pieces, which piece, if any, among the resulting three will inherit thee parent's? Should rebase, cherry-pick, and replay behave the same way (IIRC, rebase and cherry-pick behaves differently while propagating notes). Etc., etc.