Linux maintainer tooling and workflows
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: tools@kernel.org
Subject: Re: b4 review workflow issue with partially accepted serieses
Date: Wed, 10 Jun 2026 12:11:51 +0100	[thread overview]
Message-ID: <ailGd8akixhx_GHg@sirena.co.uk> (raw)
In-Reply-To: <178104250404.112711.2880594121343252200.b4-reply@b4>

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

On Tue, Jun 09, 2026 at 10:01:44PM +0000, Konstantin Ryabitsev wrote:

> You can then review it again to take more patches or do anything else
> with a series that is being reviewed. If you take a subset of patches
> again, the series will go back to the "partial" state. If you take them
> all, it will go to "accepted".

> From the action menu a "partial" series offers everything a "reviewing"
> series does: take remaining patches, rebase, range-diff, upgrade to a
> newer revision, snooze, mark as waiting, abandon, archive, thank, etc.

Yeah, so the not being able to send thanks is actually blocking the
usual flow - as well as not sending the thanks mail the tool doesn't
understand that you might have no intention of taking the remaining
patches at all so there's no way to say "I'm done with this now, send
the thanks", you can just archive the series or return it to reviewing.

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

  parent reply	other threads:[~2026-06-10 11:11 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-05  0:26 b4 review workflow issue with partially accepted serieses Mark Brown
2026-06-09 22:01 ` Konstantin Ryabitsev
2026-06-09 22:44   ` Mark Brown
2026-06-10 11:11   ` Mark Brown [this message]
2026-06-10 13:46     ` Konstantin Ryabitsev
2026-06-10 15:25       ` Mark Brown
2026-06-10 15:35         ` Konstantin Ryabitsev
2026-06-10 15:45           ` Mark Brown
2026-06-10 15:53             ` Konstantin Ryabitsev

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=ailGd8akixhx_GHg@sirena.co.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