From: Eric Wong <e@80x24.org>
To: meta@public-inbox.org
Cc: Askar Safin <safinaskar@gmail.com>
Subject: [PATCH 0/2] www: re-sort messages for strict|loose matches
Date: Mon, 1 Jan 2024 01:07:47 +0000 [thread overview]
Message-ID: <20240101010749.1859763-1-e@80x24.org> (raw)
1/2 fixes the bug reported by Askar Safin, while 2/2 makes
the multi-rootedness of threads which triggered the bug more
obvious.
Both patches deployed to my lore mirror at yhbt.net/lore:
https://yhbt.net/lore/lkml/20231120011248.396012-1-stefanb@linux.ibm.com/T/
Eric Wong (2):
over: re-sort Subject matches for WWW /T/ endpoint
view: always show strict|loose note w/ multi-roots
lib/PublicInbox/Over.pm | 5 +++++
lib/PublicInbox/View.pm | 2 +-
2 files changed, 6 insertions(+), 1 deletion(-)
next reply other threads:[~2024-01-01 1:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-01 1:07 Eric Wong [this message]
2024-01-01 1:07 ` [PATCH 1/2] over: re-sort Subject matches for WWW /T/ endpoint Eric Wong
2024-01-01 1:07 ` [PATCH 2/2] view: always show strict|loose note w/ multi-roots Eric Wong
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
List information: https://public-inbox.org/README
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20240101010749.1859763-1-e@80x24.org \
--to=e@80x24.org \
--cc=meta@public-inbox.org \
--cc=safinaskar@gmail.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).