unofficial mirror of meta@public-inbox.org
 help / color / mirror / Atom feed
From: Eric Wong <e@80x24.org>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: meta@public-inbox.org
Subject: Re: boost and /all/
Date: Mon, 2 Aug 2021 22:08:50 +0000	[thread overview]
Message-ID: <20210802220850.GA3015@dcvr> (raw)
In-Reply-To: <20210802212923.3hnishr2xeuqhgpk@nitro.local>

Konstantin Ryabitsev <konstantin@linuxfoundation.org> wrote:
> On Mon, Aug 02, 2021 at 09:16:56PM +0000, Eric Wong wrote:
> > > I believe this should assign boost value of 0, but the virtualization source
> > > seems to be "winning" both via the interface and when retrieving t.mbox.gz.
> > > Anything I'm not doing right?
> > 
> > Correct, boost=0 is the default.  Did you set boost before indexing?
> > It needs to be set before indexing (or reindexing).
> 
> Yes, all boost values were present from the start. On this particular
> instance, I ended up indexing a few tiny lists first, and then /lkml/, and
> only after that the remaining bulk of repositories, so this thread would have
> first made its way in through /lkml/ and then through most other lists,
> including /virtualization/. That shouldn't have caused /virtualization/ to
> "win", should it?

Oops, yes, there seems to be a bug across multiple invocations
(but not reindex), will try to fix it in a few.

      reply	other threads:[~2021-08-02 22:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-02 20:40 boost and /all/ Konstantin Ryabitsev
2021-08-02 21:16 ` Eric Wong
2021-08-02 21:29   ` Konstantin Ryabitsev
2021-08-02 22:08     ` Eric Wong [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=20210802220850.GA3015@dcvr \
    --to=e@80x24.org \
    --cc=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).