From: Mark Brown <broonie@kernel.org>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: tools@kernel.org
Subject: Finding older versions when adding tracking
Date: Wed, 25 Mar 2026 11:41:10 +0000 [thread overview]
Message-ID: <43fde53a-4e7c-487a-9a09-e9d8549bd888@sirena.org.uk> (raw)
[-- Attachment #1: Type: text/plain, Size: 362 bytes --]
Hi,
I just did a b4 review track on 20260325101437.3059693-1-sheetal@nvidia.com
and it added a new series, discovering the prior v1 and v2 which had
been single patches. However, I was already tracking v2 - I would have
expected the logic that determines that a series is already tracked
would have kicked in but it didn't and I got a duplicate.
Thanks,
Mark
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
reply other threads:[~2026-03-25 11:41 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=43fde53a-4e7c-487a-9a09-e9d8549bd888@sirena.org.uk \
--to=broonie@kernel.org \
--cc=konstantin@linuxfoundation.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