From: B4 Bugbot <bugbot+b4@kernel.org>
To: mricon@kernel.org, tools@kernel.org, broonie@kernel.org
Subject: Re: b4 review handing of rebasing issues for new versions
Date: Wed, 18 Mar 2026 13:49:53 +0000 (UTC) [thread overview]
Message-ID: <20260318-b4a2fb75c2-7ac9eb879be3@git.kernel.org> (raw)
In-Reply-To: <069aac52-a9a2-44e1-bdbb-eabc82e23641@sirena.org.uk>
Konstantin Ryabitsev writes in commit fed4cd88f9dc9b7370fcdb292aa27ecf40626635:
review: do not re-promote waiting series for already-known versions
When a newer version of a series fails to apply and the maintainer
puts the series back into waiting, the next update cycle would
immediately wake it up again because the (broken) version is still
newer than the checked-out revision. Fix this by comparing discovered
versions against what was already known in the revisions database
before this update cycle, rather than against the applied revision.
This means a waiting series is only promoted when a genuinely new
version appears — one that was not already recorded in the database.
Reported-by: Mark Brown <broonie@kernel.org>
Closes: https://msgid.link/069aac52-a9a2-44e1-bdbb-eabc82e23641@sirena.org.uk # 4a2fb75
Signed-off-by: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Assisted-by: claude-opus-4-6-20250904
--
Deet-doot-dot, I am a bot.
b4 bug tracker (bugspray 0.1-dev)
next prev parent reply other threads:[~2026-03-18 13:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-17 19:13 b4 review handing of rebasing issues for new versions Mark Brown
2026-03-17 19:52 ` Konstantin Ryabitsev
2026-03-17 19:58 ` B4 Bugbot
2026-03-18 13:49 ` B4 Bugbot [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-03-17 19:22 Sorting for applied and thanked reviews Mark Brown
2026-03-17 21:03 ` Konstantin Ryabitsev
2026-03-17 22:21 ` Mark Brown
2026-03-18 14:17 ` Konstantin Ryabitsev
2026-03-18 19:45 ` Mark Brown
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=20260318-b4a2fb75c2-7ac9eb879be3@git.kernel.org \
--to=bugbot+b4@kernel.org \
--cc=broonie@kernel.org \
--cc=mricon@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