All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: users@linux.kernel.org, tools@linux.kernel.org
Subject: Re: lore.kernel.org upgrade: Sep 1, 2021
Date: Mon, 30 Aug 2021 12:47:33 -0500	[thread overview]
Message-ID: <CAL_JsqL3+HmAReo9PTLW4Y1o_NiR6oZrV+FC+msGu+epkAJ02g@mail.gmail.com> (raw)
In-Reply-To: <20210830164626.tq5emfrht4o46x33@nitro.local>

On Mon, Aug 30, 2021 at 11:46 AM Konstantin Ryabitsev
<konstantin@linuxfoundation.org> wrote:
>
> Hi, all:
>
> 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).

There's also a ton of stable review patches, but that's not a new
thing as those are cross posted. While I can filter both of those
out[2], having to do that doesn't seem like the greatest default
behaviour.

Rob

[1] https://x-lore.kernel.org/all/?q=rseq+arm64+perf
[2] https://x-lore.kernel.org/all/?q=rseq+arm64+perf+-l%3Astable+-f%3Adevnull%40kernel.org

  reply	other threads:[~2021-08-30 17:47 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 [this message]
2021-08-30 18:04   ` Konstantin Ryabitsev
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=CAL_JsqL3+HmAReo9PTLW4Y1o_NiR6oZrV+FC+msGu+epkAJ02g@mail.gmail.com \
    --to=robh@kernel.org \
    --cc=konstantin@linuxfoundation.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.