user/dev discussion of public-inbox itself
 help / color / mirror / code / Atom feed
From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: Eric Wong <e@80x24.org>
Cc: meta@public-inbox.org
Subject: Re: [PATCH] view: distinguish strict and loose thread matches
Date: Mon, 6 Aug 2018 16:05:44 -0400	[thread overview]
Message-ID: <f901d99c-5a56-d97c-a19a-07f3e62d4ab8@linuxfoundation.org> (raw)
In-Reply-To: <20180805060440.fhl7zvyis246e3ym@dcvr>


[-- Attachment #1.1: Type: text/plain, Size: 700 bytes --]

On 08/05/18 02:04, Eric Wong wrote:
> The "loose" (Subject:-based) thread matching yields too many
> hits for some common subjects (e.g. "[GIT] Networking" on LKML)
> and causes thread skeletons to not show the current messages.
> Favor strict matches in the query and only add loose matches
> if there's space.

Eric:

I've updated to ce5494b5b83 and reindexed, but it appears that I still
have the same behaviour as previously:

https://lore.kernel.org/lkml/20180805.004744.1043412275329854518.davem@davemloft.net/

Are there any configuration file changes that are required for this?

Best,
-- 
Konstantin Ryabitsev
Director, IT Infrastructure Security
The Linux Foundation


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

  parent reply	other threads:[~2018-08-06 20:05 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-03 18:26 Threading/searching problem Konstantin Ryabitsev
2018-08-03 19:20 ` Eric Wong
2018-08-03 19:38   ` Konstantin Ryabitsev
2018-08-05  6:04     ` [PATCH] view: distinguish strict and loose thread matches Eric Wong
2018-08-05  8:19       ` [RFC] overidx: preserve `tid' column on re-indexing Eric Wong
2018-08-05 21:41         ` Eric Wong
2018-08-06 20:05       ` Konstantin Ryabitsev [this message]
2018-08-06 20:10         ` [PATCH] view: distinguish strict and loose thread matches 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=f901d99c-5a56-d97c-a19a-07f3e62d4ab8@linuxfoundation.org \
    --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).