From: "Vlastimil Babka (SUSE)" <vbabka@kernel.org>
To: tools@linux.kernel.org
Subject: possible fuzziness for b4 trailers -u?
Date: Thu, 18 Jun 2026 10:50:52 +0200 [thread overview]
Message-ID: <b0e433ff-fa15-4715-ae0a-7f23da217d51@kernel.org> (raw)
Hi,
I sometimes run b4 trailers -u to collect tags on patches that have been
meanwhile slightly modified in git since the posting. Sometimes it's on the
b4/$cover_topic branch as a submitter, sometimes it's already applied (but
not stable as in no history rewrite) on a maintainer tree branch (I do use
--since-commit and doublecheck the result of the update closely since some
past surprises...).
AFAICS the trailers update relies only patch-id (?) so it will miss the tags
when patch-id changes due to these local modifications. Could it try some
fuzzy matching in that case? Some ideas:
- in b4/$cover_topic branch the metadata allows finding the posting thread
and matching the patch subject
- ok, subject can sometimes change too, but not so often as the code
- in maintainer tree branch, there's usually a patch.msgid.link Link: that
can lead to the given patch rather deterministically.
Thanks for consideration!
Vlastimil
next reply other threads:[~2026-06-18 8:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-18 8:50 Vlastimil Babka (SUSE) [this message]
2026-06-18 18:30 ` possible fuzziness for b4 trailers -u? Konstantin Ryabitsev
2026-07-08 16:16 ` Vlastimil Babka (SUSE)
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=b0e433ff-fa15-4715-ae0a-7f23da217d51@kernel.org \
--to=vbabka@kernel.org \
--cc=tools@linux.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