From: Junio C Hamano <gitster@pobox.com>
To: Nico Williams <nico@cryptonector.com>
Cc: Matt Stark <msta@google.com>,
git@vger.kernel.org, ps@pks.im, phillip.wood@dunelm.org.uk,
Martin von Zweigbergk <martinvonz@google.com>,
remo@buenzli.dev, Edwin Kempin <ekempin@google.com>,
schacon@gmail.com, philipmetzger@bluewin.ch,
konstantin@linuxfoundation.org, newren@gmail.com,
tytso@mit.edu, rikingcoding@gmail.com
Subject: Re: [PATCH] headers: Preserve 'change-id' header in rebase / cherry-pick.
Date: Tue, 07 Apr 2026 07:33:14 -0700 [thread overview]
Message-ID: <xmqqh5pm7sd1.fsf@gitster.g> (raw)
In-Reply-To: <adSPznztKWo63Tjr@ubby> (Nico Williams's message of "Tue, 7 Apr 2026 00:02:06 -0500")
Nico Williams <nico@cryptonector.com> writes:
> On Mon, Apr 06, 2026 at 11:58:19PM -0500, Nico Williams wrote:
>> Maybe that's the trick: local configuration for determining the
>> copy-or-drop semantic for different operations, and maybe hooks for
>> altering when copying. [...]
>
> I should add that I would want an original-change-id header that could
> be used (again, optionally) to relate commits that get cherry-picked or
> rebased but end up having different change-ids.
With these people with (possibly just slightly) different wants
different project may have, wouldn't it work to record this kind of
random pieces of information either in notes (the benefit being that
it can be corrected without having to rewrite history) or in
trailers?
next prev parent reply other threads:[~2026-04-07 14:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-07 3:13 [PATCH] headers: Preserve 'change-id' header in rebase / cherry-pick Matt Stark
2026-04-07 4:09 ` Junio C Hamano
2026-04-07 4:58 ` Nico Williams
2026-04-07 5:02 ` Nico Williams
2026-04-07 14:33 ` Junio C Hamano [this message]
2026-04-07 9:55 ` Phillip Wood
2026-04-07 15:52 ` Nico Williams
2026-04-07 16:20 ` Junio C Hamano
2026-04-07 20:13 ` Nico Williams
2026-04-07 14:42 ` Junio C Hamano
2026-04-07 9:41 ` Phillip Wood
2026-04-07 23:28 ` brian m. carlson
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=xmqqh5pm7sd1.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=ekempin@google.com \
--cc=git@vger.kernel.org \
--cc=konstantin@linuxfoundation.org \
--cc=martinvonz@google.com \
--cc=msta@google.com \
--cc=newren@gmail.com \
--cc=nico@cryptonector.com \
--cc=philipmetzger@bluewin.ch \
--cc=phillip.wood@dunelm.org.uk \
--cc=ps@pks.im \
--cc=remo@buenzli.dev \
--cc=rikingcoding@gmail.com \
--cc=schacon@gmail.com \
--cc=tytso@mit.edu \
/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