From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: Eric Wong <e@80x24.org>
Cc: meta@public-inbox.org
Subject: Re: [PATCH] www: use correct threadid for per-thread search
Date: Wed, 21 Jun 2023 13:11:54 -0400 [thread overview]
Message-ID: <20230621-reversion-bullseye-24a038@meerkat> (raw)
In-Reply-To: <20230616231301.M394415@dcvr>
On Fri, Jun 16, 2023 at 11:13:01PM +0000, Eric Wong wrote:
> > Reviving this old thread for some clarification. I noticed that this only
> > works for /all/, but not for individual inboxes. E.g.:
> >
> > $ curl -d '' -sSf \
> > https://lore.kernel.org/all/"$MSGID/?x=m&q=rt:2023-03-29.." \
> > | zgrep -i ^Message-ID:
> > Message-ID: <cfcf852c-e9f0-f560-542d-0f72777a85b2@leemhuis.info>
> >
> > but with /lkml/ I get a 404:
> >
> > $ curl -d '' -sSf \
> > https://lore.kernel.org/lkml/"$MSGID/?x=m&q=rt:2023-03-29.." \
> > | zgrep -i ^Message-ID:
> > curl: (22) The requested URL returned error: 404
> >
> > Is that intentionally restricted to just extindex?
>
> It's a bug, fix below and deployed to https://80x24.org/lore/
Indeed, looks good now. Thank you!
-K
prev parent reply other threads:[~2023-06-21 17:11 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-27 15:08 Cheap way to check for new messages in a thread Konstantin Ryabitsev
2023-03-27 19:10 ` Eric Wong
2023-03-27 20:47 ` Konstantin Ryabitsev
2023-03-27 21:38 ` Eric Wong
2023-03-28 14:04 ` Konstantin Ryabitsev
2023-03-28 19:45 ` Eric Wong
2023-03-28 20:00 ` Konstantin Ryabitsev
2023-03-28 22:08 ` Eric Wong
2023-03-28 23:30 ` Konstantin Ryabitsev
2023-03-29 21:25 ` Eric Wong
2023-03-30 11:29 ` Eric Wong
2023-03-30 16:45 ` Konstantin Ryabitsev
2023-03-31 1:40 ` Eric Wong
2023-04-11 11:27 ` Eric Wong
2023-06-16 19:11 ` Konstantin Ryabitsev
2023-06-16 23:13 ` [PATCH] www: use correct threadid for per-thread search Eric Wong
2023-06-21 17:11 ` 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
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=20230621-reversion-bullseye-24a038@meerkat \
--to=konstantin@linuxfoundation.org \
--cc=e@80x24.org \
--cc=meta@public-inbox.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).