From: Eric Wong <e@80x24.org>
To: Konstantin Ryabitsev <mricon@kernel.org>
Cc: "Jason A. Donenfeld" <Jason@zx2c4.com>,
tools@linux.kernel.org, stable@vger.kernel.org,
meta@public-inbox.org, sashal@kernel.org,
gregkh@linuxfoundation.org, krzk@kernel.org
Subject: Re: filtering stable patches in lore queries
Date: Wed, 8 May 2024 17:09:27 +0000 [thread overview]
Message-ID: <20240508170927.M233061@dcvr> (raw)
In-Reply-To: <20240508-optimal-peach-bustard-a49160@meerkat>
Konstantin Ryabitsev <mricon@kernel.org> wrote:
> On Wed, May 08, 2024 at 11:33:14AM GMT, Eric Wong wrote:
> > https://public-inbox.org/meta/20240508110957.3108196-1-e@80x24.org/
> > Yeah, though there's 3 ways of indexing strings, currently :x
> > I've decided to keep some options open and support boolean_term,
> > text, and phrase for now.
>
> What's the difference between "text" and "phrase"?
text is like indexlevel=medium (case-insensitive and sortable
by relevance), while phrase is like indexlevel=full so
adds positions to allow searching phrases via "double quotesk
(also documented in the proposed public-inbox-config.pod change,
not sure how clear it was for non-Xapian-internals-aware
folks...)
> > boolean_term is the cheapest and probably best for exactly
> > matching labels/enums and such.
>
> So, this is for "X-Ignore-Me: Yes" type of headers?
Yes. Though I just remembered it's case-sensitive (same
treatment as Message-ID with "m:"), so I guess that needs to be
documented.
prev parent reply other threads:[~2024-05-08 17:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-27 0:28 filtering stable patches in lore queries Jason A. Donenfeld
2024-04-27 7:19 ` Eric Wong
2024-04-29 14:27 ` Konstantin Ryabitsev
2024-05-08 11:33 ` Eric Wong
2024-05-08 17:01 ` Konstantin Ryabitsev
2024-05-08 17:09 ` 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=20240508170927.M233061@dcvr \
--to=e@80x24.org \
--cc=Jason@zx2c4.com \
--cc=gregkh@linuxfoundation.org \
--cc=krzk@kernel.org \
--cc=meta@public-inbox.org \
--cc=mricon@kernel.org \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.org \
--cc=tools@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.
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).