From: Nico Williams <nico@cryptonector.com>
To: phillip.wood@dunelm.org.uk
Cc: Junio C Hamano <gitster@pobox.com>, Matt Stark <msta@google.com>,
git@vger.kernel.org, ps@pks.im,
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, 7 Apr 2026 10:52:39 -0500 [thread overview]
Message-ID: <adUoR/T17fKr+YLN@ubby> (raw)
In-Reply-To: <68e5a1eb-ec7b-43ca-98d1-ffdf7fef013f@gmail.com>
On Tue, Apr 07, 2026 at 10:55:00AM +0100, Phillip Wood wrote:
> On 07/04/2026 05:58, 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 think the danger with making it configurable is that you cannot rely on
> the semantics because they vary between commits created by different
> authors. [...]
Well, I said "site-local" and "for some definition of site", and the one
I had in mind is that the upstream provides this [default] configuration
for clones. Sure, authors could override this locally, but presumably
they wouldn't, and presumably upstreams would check for adherence to
their rules.
> [...]. If we could get agreement on
That's proven difficult to do.
Nico
--
next prev parent reply other threads:[~2026-04-07 15:52 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
2026-04-07 9:55 ` Phillip Wood
2026-04-07 15:52 ` Nico Williams [this message]
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=adUoR/T17fKr+YLN@ubby \
--to=nico@cryptonector.com \
--cc=ekempin@google.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=konstantin@linuxfoundation.org \
--cc=martinvonz@google.com \
--cc=msta@google.com \
--cc=newren@gmail.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