From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: meta@public-inbox.org
Subject: Boosts still not quite working
Date: Sat, 14 Aug 2021 09:46:09 -0400 [thread overview]
Message-ID: <20210814134609.jcgq7je3yq4agzn6@nitro.local> (raw)
Eric:
The new x-lore systems are rebuilt and reindexed using the latest master (as
of 2 days ago), but boosts still don't appear to be quite working as intended.
For example, this thread:
https://x-lore.kernel.org/all/20210809175620.720923-1-ltykernel@gmail.com/
It was sent to iommu@lists.linux-foundation.org (mailman) and to a bunch of
vger lists, all of which have higher boosts in the configuration, e.g. netdev:
[publicinbox "linux-iommu"]
address = iommu@lists.linux-foundation.org
url = https://x-lore.kernel.org/linux-iommu/
inboxdir = /srv/public-inbox/lore.kernel.org/linux-iommu
indexlevel = full
newsgroup = org.linux-foundation.lists.iommu
infourl = https://www.kernel.org/lore.html
boost = 1
listid = iommu.lists.linux-foundation.org
[publicinbox "netdev"]
address = netdev@vger.kernel.org
url = https://x-lore.kernel.org/netdev/
inboxdir = /srv/public-inbox/lore.kernel.org/netdev
indexlevel = full
newsgroup = org.kernel.vger.netdev
infourl = https://www.kernel.org/lore.html
boost = 10
listid = netdev.vger.kernel.org
When retrieving mbox.gz, we get the contents as archived by the iommu list,
though theoretically we should get one of the higher-boosted lists instead.
Anything I can help troubleshoot?
This was indexed from scratch with all repositories already in place.
Best regards,
-K
next reply other threads:[~2021-08-14 13:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-14 13:46 Konstantin Ryabitsev [this message]
2021-08-14 20:46 ` Boosts still not quite working Eric Wong
2021-08-14 22:09 ` 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
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=20210814134609.jcgq7je3yq4agzn6@nitro.local \
--to=konstantin@linuxfoundation.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).