From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: Eric Wong <e@80x24.org>
Cc: meta@public-inbox.org
Subject: Re: Troubleshooting threads missing from /all/
Date: Tue, 5 Oct 2021 14:03:24 -0400 [thread overview]
Message-ID: <20211005180324.3miboond7ubth5v5@meerkat.local> (raw)
In-Reply-To: <20211005043954.GA23990@dcvr>
On Tue, Oct 05, 2021 at 04:39:54AM +0000, Eric Wong wrote:
> Eric Wong <e@80x24.org> wrote:
> > b) just reindex in place (it /should/ work...)
>
> I reindexing live on yhbt/lore and it didn't break...
>
> Btw, did you see my other questions about whether or not boost
> was in use?
Yes, but I was attending the Linux Security Summit last week, so my attention
was all over the place. We do use boost values there. Looking at that
particular message, it was sent to regressions and linux-wireless, which have
different boost values:
[publicinbox "regressions"]
address = regressions@lists.linux.dev
url = regressions
inboxdir = /srv/public-inbox/lore.kernel.org/regressions
indexlevel = full
newsgroup = dev.linux.lists.regressions
boost = 11
listid = regressions.lists.linux.dev
[publicinbox "linux-wireless"]
address = linux-wireless@vger.kernel.org
url = linux-wireless
inboxdir = /srv/public-inbox/lore.kernel.org/linux-wireless
indexlevel = full
newsgroup = org.kernel.vger.linux-wireless
boost = 10
listid = linux-wireless.vger.kernel.org
we give lists.linux.dev a higher boost value because we populate it straight
from watched mlmmj archive dirs and it's more likely to have "truest" headers.
-K
next prev parent reply other threads:[~2021-10-05 18:03 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-01 13:05 Troubleshooting threads missing from /all/ Konstantin Ryabitsev
2021-10-01 19:58 ` Eric Wong
2021-10-01 20:08 ` Konstantin Ryabitsev
2021-10-01 20:41 ` Eric Wong
2021-10-01 20:49 ` Konstantin Ryabitsev
2021-10-01 20:54 ` Eric Wong
2021-10-01 20:58 ` Konstantin Ryabitsev
2021-10-01 22:25 ` Eric Wong
2021-10-01 22:27 ` Eric Wong
2021-10-01 23:11 ` Konstantin Ryabitsev
2021-10-01 23:46 ` Eric Wong
2021-10-02 0:02 ` Eric Wong
2021-10-05 4:39 ` Eric Wong
2021-10-05 18:03 ` Konstantin Ryabitsev [this message]
2021-10-06 10:18 ` Eric Wong
2021-10-07 8:36 ` Eric Wong
2021-10-07 13:57 ` Konstantin Ryabitsev
2021-10-07 21:36 ` Eric Wong
2021-10-07 21:33 ` Eric Wong
2021-10-07 21:33 ` Eric Wong
2021-10-08 17:33 ` Konstantin Ryabitsev
2021-10-08 21:34 ` Eric Wong
2021-10-16 9:43 ` Eric Wong
2021-10-17 18:04 ` Konstantin Ryabitsev
2021-10-17 23:12 ` Eric Wong
2021-10-18 5:25 ` Eric Wong
2021-10-18 14:04 ` Konstantin Ryabitsev
2021-10-18 14:03 ` Konstantin Ryabitsev
2021-10-24 0:03 ` Eric Wong
2021-10-26 21:11 ` Konstantin Ryabitsev
2021-10-29 10:18 ` release updates [was: Troubleshooting threads missing from /all/] Eric Wong
2021-10-01 20:17 ` Troubleshooting threads missing from /all/ Konstantin Ryabitsev
2021-10-02 11:39 ` 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=20211005180324.3miboond7ubth5v5@meerkat.local \
--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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/public-inbox.git
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).