From: Konstantin Ryabitsev <mricon@kernel.org>
To: Eric Wong <e@80x24.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 13:01:00 -0400 [thread overview]
Message-ID: <20240508-optimal-peach-bustard-a49160@meerkat> (raw)
In-Reply-To: <20240508113314.M238016@dcvr>
On Wed, May 08, 2024 at 11:33:14AM GMT, Eric Wong wrote:
> > I'm whole-heartedly for this! This ties nicely to my b4 work where I'd
> > like to be able to identify code-review trailers sent for a specific
> > patch, even if that patch itself is not on lore. For example, this could
> > be a patch that is part of a pull-request on a git forge, but we'd still
> > like to be able to collect and find code-review trailers for it when a
> > maintainer applies it.
>
> OK, a more configurable version is available on a per-inbox basis:
>
> https://public-inbox.org/meta/20240508110957.3108196-1-e@80x24.org/
>
> But that's a PITA to configure with hundreds of inboxes and
> doesn't have extindex support, yet.
>
> I made it share logic with the old altid code; so I'll also be
> getting altid into extindex since ISTR users wanting to be able
> to lookup gmane stuff via extindex.
Great, thanks for doing this. I'll wait until this has extindex support,
because I really need to be able to look across all inboxes.
> 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"?
> 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?
-K
next prev parent reply other threads:[~2024-05-08 17:01 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 [this message]
2024-05-08 17:09 ` 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=20240508-optimal-peach-bustard-a49160@meerkat \
--to=mricon@kernel.org \
--cc=Jason@zx2c4.com \
--cc=e@80x24.org \
--cc=gregkh@linuxfoundation.org \
--cc=krzk@kernel.org \
--cc=meta@public-inbox.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.
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).