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@xxxxxxxxx/ > > 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
