From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <konstantin@linuxfoundation.org>
X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on dcvr.yhbt.net
X-Spam-Level: 
X-Spam-ASN:  
X-Spam-Status: No, score=-3.6 required=3.0 tests=BAYES_00,DKIMWL_WL_HIGH,
	DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,
	RCVD_IN_DNSWL_HI,SPF_HELO_NONE,SPF_PASS shortcircuit=no autolearn=ham
	autolearn_force=no version=3.4.6
Received: from sin.source.kernel.org (sin.source.kernel.org [IPv6:2604:1380:40e1:4800::1])
	(using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)
	 key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256)
	(No client certificate requested)
	by dcvr.yhbt.net (Postfix) with ESMTPS id 47E681F44D
	for <meta@public-inbox.org>; Wed,  8 May 2024 17:01:04 +0000 (UTC)
Authentication-Results: dcvr.yhbt.net;
	dkim=pass (2048-bit key; unprotected) header.d=kernel.org header.i=@kernel.org header.a=rsa-sha256 header.s=k20201202 header.b=bdPge6OZ;
	dkim-atps=neutral
Received: from smtp.kernel.org (transwarp.subspace.kernel.org [100.75.92.58])
	by sin.source.kernel.org (Postfix) with ESMTP id 775DBCE195B;
	Wed,  8 May 2024 17:01:02 +0000 (UTC)
Received: by smtp.kernel.org (Postfix) with ESMTPSA id 93B29C113CC;
	Wed,  8 May 2024 17:01:01 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org;
	s=k20201202; t=1715187661;
	bh=yIcIect25By+5l9xSTVJF8N1/7X96wDUI0owYNYZGRM=;
	h=Date:From:To:Cc:Subject:References:In-Reply-To:From;
	b=bdPge6OZAXT6FYQ9UmtY/IHpEqmhPZEidxOKZhfh6qBXq+3WyJ1jb/rtWi1pG6rR/
	 Lh3ozTfg2qfvGm1PdJkk/LmuavlEcFvl4tIjA0WZqYIUnNUhdxc5t616hp7GtpkVEt
	 PCQxUIsQcEttmccFJtpq0d24P/89VluAAkAgc4mnoXEDBkYp+WVh8A+GflhjbUJQWt
	 r/wLEuHBZQDCOVjP4AX6uukWS8Hdcufe5X/Wle52m5s54br1A4uibyP79ynEu/o55W
	 i61v9VqOogjRP6EbtERJTZ4oveCD5tTPD7QL9wDOAcP/Y8c+6mJ188xHpmECEKmtNA
	 rlvwFul2blOTg==
Date: Wed, 8 May 2024 13:01:00 -0400
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
Message-ID: <20240508-optimal-peach-bustard-a49160@meerkat>
References: <ZixGx_sTyDmdUlaV@zx2c4.com>
 <20240427071921.M438650@dcvr>
 <20240429-antique-hyena-of-glee-d9e4ac@lemur>
 <20240508113314.M238016@dcvr>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <20240508113314.M238016@dcvr>
List-Id: <meta.public-inbox.org>

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