From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: Rob Herring <robh@kernel.org>
Cc: users@linux.kernel.org, tools@linux.kernel.org
Subject: Re: lore.kernel.org upgrade: Sep 1, 2021
Date: Mon, 30 Aug 2021 14:04:23 -0400 [thread overview]
Message-ID: <20210830180423.przc3a63vhseefne@nitro.local> (raw)
In-Reply-To: <CAL_JsqL3+HmAReo9PTLW4Y1o_NiR6oZrV+FC+msGu+epkAJ02g@mail.gmail.com>
On Mon, Aug 30, 2021 at 12:47:33PM -0500, Rob Herring wrote:
> > My tests of the new lore.kernel.org service (currently running on
> > x-lore.kernel.org) are looking good, so I will be putting that into production
> > on Wednesday, September 1, 2021.
>
> One thing I've noticed doing some searches[1] is I get a bunch of hits
> on post-receive-hook mails dominating the results which doesn't seem
> too useful. Do those need to be in the 'all' index? The purpose of
> them is pretty orthogonal to development patches and discussions. Or
> is it possible to have an 'almost-all' index? Or other flavors of
> indexes in general? Perhaps a patches only index for example (the best
> I found for a query is 'dfn:/', but that has some false positives).
I do agree that adding the gitolite feed there was a bad choice -- I'll
probably eject it from lore and let it just live on git.kernel.org.
Regarding custom combined indexes, this is something that I will be
working on in the near future. One of the new features in public-inbox is the
"lei" (local email interface) command, which lets you collect email from
multiple sources (your local inbox, lore.kernel.org feeds, nntp group, an imap
connection, etc) based on specific search criteria. I've not yet decided how
we're going to provide this for others, but the goal is to make it easy for
maintainers to define their own custom feeds and share it with co-maintainers
(or anyone else). Once I have a clearer picture on how I want to go ahead,
I'll follow up with others here.
-K
next prev parent reply other threads:[~2021-08-30 18:04 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-30 16:46 lore.kernel.org upgrade: Sep 1, 2021 Konstantin Ryabitsev
2021-08-30 17:47 ` Rob Herring
2021-08-30 18:04 ` Konstantin Ryabitsev [this message]
2021-09-01 1:23 ` Darrick J. Wong
2021-09-01 9:28 ` Josh Triplett
2021-09-01 13:44 ` Konstantin Ryabitsev
2021-09-01 13:12 ` Sebastian Andrzej Siewior
2021-09-01 13:25 ` Konstantin Ryabitsev
2021-09-15 12:05 ` Sebastian Andrzej Siewior
2021-09-15 12:15 ` Konstantin Ryabitsev
2021-09-15 13:00 ` Sebastian Andrzej Siewior
2021-09-15 13:04 ` Konstantin Ryabitsev
2021-09-02 18:45 ` Guenter Roeck
2021-09-02 18:56 ` Konstantin Ryabitsev
2021-09-02 19:12 ` Guenter Roeck
2021-09-09 9:58 ` David Howells
2021-09-09 12:31 ` Konstantin Ryabitsev
2021-09-09 12:50 ` Steven Rostedt
2021-09-09 13:21 ` Geert Uytterhoeven
2021-09-09 14:33 ` Theodore Ts'o
2021-09-09 14:48 ` Konstantin Ryabitsev
2021-09-09 13:54 ` David Howells
2021-09-09 14:37 ` 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=20210830180423.przc3a63vhseefne@nitro.local \
--to=konstantin@linuxfoundation.org \
--cc=robh@kernel.org \
--cc=tools@linux.kernel.org \
--cc=users@linux.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.