From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: Eric Wong <e@80x24.org>
Cc: Alison Schofield <alison.schofield@intel.com>,
meta@public-inbox.org, Dave Hansen <dave.hansen@intel.com>
Subject: Re: Threaded responses to queries (x86)
Date: Wed, 31 May 2023 08:05:43 -0400 [thread overview]
Message-ID: <20230531-reprise-stargazer-5078af@meerkat> (raw)
In-Reply-To: <20230531075053.M93596@dcvr>
On Wed, May 31, 2023 at 07:50:53AM +0000, Eric Wong wrote:
> I wonder if lore can expose x86@kernel.org as its own inbox even
> if it's technically not a subscribable mailing list. That would
> be much faster (but less space-efficient) than issuing a Xapian
> query to get x86@kernel.org mails.
I'm not even sure why it's not a real list. Let me follow up with them to see
if we should just convert it.
-K
prev parent reply other threads:[~2023-05-31 12:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-25 18:56 Threaded responses to queries (x86) Alison Schofield
2023-05-31 7:50 ` Eric Wong
2023-05-31 12:05 ` 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=20230531-reprise-stargazer-5078af@meerkat \
--to=konstantin@linuxfoundation.org \
--cc=alison.schofield@intel.com \
--cc=dave.hansen@intel.com \
--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).