From: Dan Williams <dan.j.williams@intel.com>
To: konstantin@linuxfoundation.org
Cc: ksummit@lists.linux.dev, workflows@vger.kernel.org
Subject: [PATCH 0/3] b4: Add git notes for submission link trailers
Date: Tue, 14 Oct 2025 00:15:27 -0700 [thread overview]
Message-ID: <20251014071530.3665691-1-dan.j.williams@intel.com> (raw)
As detailed in patch3, after the fact / dynamic lore link generation
continues to be awkward for managing work-in-progress patches across
multiple versions. 'git notes' allows for workflow specific metadata
that does not pollute upstream. The other desirable feature of notes is
that they are displayed by default in cgit.
So the mainline history and upstream pull-requests remain clean, but
work-in-progress series development can readily display which commits
came from which messages.
Example:
$ b4 shazam -L 20250815010645.2980846-1-alison.schofield@intel.com
$ git show | grep -A1 Notes
Notes:
Link: https://patch.msgid.link/20250815010645.2980846-1-alison.schofield@intel.com
Dan Williams (3):
b4: Move linktrailer to a LoreMessage property
b4, ty: Move git_get_rev_diff to __init__ for reuse in post processing
shazam
mbox: Add a --add-link-note option to shazam
src/b4/__init__.py | 53 +++++++++++++++++++++++++-----------------
src/b4/command.py | 2 ++
src/b4/mbox.py | 58 ++++++++++++++++++++++++++++++++++++++++++++++
src/b4/ty.py | 7 +-----
4 files changed, 93 insertions(+), 27 deletions(-)
base-commit: f760a0468f91296750af072f7b3aed916f217e77
--
2.51.0
next reply other threads:[~2025-10-14 7:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-14 7:15 Dan Williams [this message]
2025-10-14 7:15 ` [PATCH 1/3] b4: Move linktrailer to a LoreMessage property Dan Williams
2025-10-14 7:15 ` [PATCH 2/3] b4, ty: Move git_get_rev_diff to __init__ for reuse in post processing shazam Dan Williams
2025-10-14 7:15 ` [PATCH 3/3] mbox: Add a --add-link-note option to shazam Dan Williams
2025-10-14 18:28 ` dan.j.williams
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=20251014071530.3665691-1-dan.j.williams@intel.com \
--to=dan.j.williams@intel.com \
--cc=konstantin@linuxfoundation.org \
--cc=ksummit@lists.linux.dev \
--cc=workflows@vger.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