From: Konstantin Ryabitsev <mricon@kernel.org>
To: Mark Brown <broonie@kernel.org>
Cc: tools@kernel.org
Subject: Re: Series revision identification issue
Date: Fri, 20 Mar 2026 12:48:52 -0400 [thread overview]
Message-ID: <20260320-nifty-awesome-llama-be809d@lemur> (raw)
In-Reply-To: <88549a4a-cc82-4200-b73b-e335cbb2b024@sirena.org.uk>
On Fri, Mar 20, 2026 at 03:12:52PM +0000, Mark Brown wrote:
> The series:
>
> https://patch.msgid.link/20260309065137.949053-1-srinivas.kandagatla@oss.qualcomm.com
>
> has a new version:
>
> https://lore.kernel.org/linux-sound/20260320144918.1685838-1-srinivas.kandagatla@oss.qualcomm.com/
>
> but b4 does not seem to notice this (there's no metadata in the series
> that'd track it, but there is the subject...).
>
> Since this sort of stuff is never going to be 100% accurate it might be
> handy to have a way of explicitly linking a new version in the UI.
I'll think of a good way to do it. Maybe we can do something like:
b4 review track <msgid> --upgrades <change-id>
bugspray tag b4/review
--
KR
next prev parent reply other threads:[~2026-03-20 16:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-20 15:12 Series revision identification issue Mark Brown
2026-03-20 16:48 ` Konstantin Ryabitsev [this message]
2026-03-20 16:52 ` B4 Bugbot
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=20260320-nifty-awesome-llama-be809d@lemur \
--to=mricon@kernel.org \
--cc=broonie@kernel.org \
--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