From: Konstantin Ryabitsev <mricon@kernel.org>
To: Mark Brown <broonie@kernel.org>
Cc: tools@kernel.org
Subject: Re: Sorting of new patches
Date: Thu, 12 Mar 2026 10:53:18 -0400 [thread overview]
Message-ID: <20260312-curious-jade-grouse-03f7d4@lemur> (raw)
In-Reply-To: <121e9897-ee29-4af1-802d-2d2f979ea0fe@sirena.org.uk>
On Thu, Mar 12, 2026 at 11:49:37AM +0000, Mark Brown wrote:
> One thing I'm noticing is that patches in the "new" state get sorted
> after patches that have had their reviews started (just above patches
> waiting for new versions), this rather buries them in the UI. It would
> be good to either sort them first (as they need initial triage) or allow
> limting by state.
Yeah, every sorting approach I've tried doesn't quite do what I want. I'm
going to revamp it again:
- list all series in a workable state at the top, sorted by last-activity:
new, reviewing, accepted, replied, thanked, etc
- list all other series at the bottom: waiting, snoozed, gone
- add a state filter to the "limit" dialog
Regards,
--
KR
prev parent reply other threads:[~2026-03-12 14:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-12 11:49 Sorting of new patches Mark Brown
2026-03-12 14:53 ` Konstantin Ryabitsev [this message]
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=20260312-curious-jade-grouse-03f7d4@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