From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: Daniel Zahka <daniel.zahka@gmail.com>
Cc: "Kernel.org Tools" <tools@kernel.org>
Subject: Re: [PATCH b4] main: ez: add option to use git notes for prep and send commands
Date: Mon, 3 Nov 2025 16:34:13 -0500 [thread overview]
Message-ID: <20251103-outrageous-rainbow-sheep-e2b0b3@lemur> (raw)
In-Reply-To: <20251103-notes-v1-1-6c5a561e4ba6@gmail.com>
On Mon, Nov 03, 2025 at 12:46:59PM -0800, Daniel Zahka wrote:
> It can be useful to keep a per-patch changelog using git notes. Allow
> git notes to be added to commits during export from the b4 prep and
> send commands.
Hi:
This has come up multiple times:
https://lore.kernel.org/tools/20250130-rich-orangutan-from-eldorado-04f621@lemur/
The answer is still the same -- until git-filter-repo does the right thing
with git notes (as in, actually preserving them on rewrites), any solution
using git notes is too fragile to consider using.
-K
next prev parent reply other threads:[~2025-11-03 21:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-03 20:46 [PATCH b4] main: ez: add option to use git notes for prep and send commands Daniel Zahka
2025-11-03 21:34 ` Konstantin Ryabitsev [this message]
2025-11-03 21:58 ` Daniel Zahka
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=20251103-outrageous-rainbow-sheep-e2b0b3@lemur \
--to=konstantin@linuxfoundation.org \
--cc=daniel.zahka@gmail.com \
--cc=tools@kernel.org \
/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