Series revision identification issue

Series revision identification issue

[Mark Brown]

[-- Attachment #1: Type: text/plain, Size: 516 bytes --]

Hi Konstantin,

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.

Thanks,
Mark

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

Re: Series revision identification issue

[Konstantin Ryabitsev]

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

Re: Series revision identification issue

[B4 Bugbot]

Hello:

This conversation is now tracked by b4 bug tracker.
There is no need to do anything else, just keep talking.

--
Deet-doot-dot, I am a bot.
b4 bug tracker (bugspray 0.1-dev)