From: "konstantin@linuxfoundation.org" <konstantin@linuxfoundation.org>
To: "Verma, Vishal L" <vishal.l.verma@intel.com>
Cc: "tools@kernel.org" <tools@kernel.org>
Subject: Re: [PATCH b4] b4: Add option to b4-send to include git-notes
Date: Tue, 24 Feb 2026 23:07:05 -0500 [thread overview]
Message-ID: <20260224-curious-shrewd-vole-4ad49c@lemur> (raw)
In-Reply-To: <cc3a0991b7031b8285b947d4fad7482fc06a1eb6.camel@intel.com>
On Wed, Feb 25, 2026 at 03:46:56AM +0000, Verma, Vishal L wrote:
> Ah good point - I should've searched for it.
>
> I see Yazen posted a follow-up[1] using a workaround from the
> discussion filter-repo issue - I can see if you consider this whole
> thing to be a bit clunky, but it would certainly be nice to have. Or is
> there another preferable way to add these 'basement' notes to patches
> while using a b4 prep/send workflow?
Yes, you can literally just amend/interactive rebase a patch and add a section
under ---. :)
--
KR
prev parent reply other threads:[~2026-02-25 4:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-25 1:01 [PATCH b4] b4: Add option to b4-send to include git-notes Vishal Verma
2026-02-25 2:54 ` Konstantin Ryabitsev
2026-02-25 3:46 ` Verma, Vishal L
2026-02-25 4:07 ` konstantin [this message]
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=20260224-curious-shrewd-vole-4ad49c@lemur \
--to=konstantin@linuxfoundation.org \
--cc=tools@kernel.org \
--cc=vishal.l.verma@intel.com \
/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