Repeatedly checking $PATH for `git' when we need to call it
multiple times in quick succession doesn't seem useful. So
avoid some expensive stat(2) syscalls to make things less bad
for systems which require expensive CPU vulnerability
mitigations.
This also saves a bunch of memory allocations
Konstantin Ryabitsev wrote:
> On Wed, May 08, 2024 at 11:33:14AM GMT, Eric Wong wrote:
> > https://public-inbox.org/meta/20240508110957.3108196-...@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,
>
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
Konstantin Ryabitsev wrote:
> On Sat, Apr 27, 2024 at 07:19:21AM GMT, Eric Wong wrote:
> > Correct, public-inbox currently won't index every header due to
> > cost, false positives, and otherwise lack of usefulness (general
> > gibberish from DKIM sigs, various UUIDs, etc).
> >
> > So it doesn't
This doesn't validate any prefix conflicts (and neither has altid
for the past 7-8 years). Thus both the user-visible lowercase
ones and indexer X-PREFIXED-ALL-CAPS ones can conflict with
prefixes already in use by our code (e.g. XTO).
And extindex support for this needs to happen...
This allows indexing arbitrary headers to allow filtering by
boolean terms or existing text rules. Disabling RFC 2047
decoding is supported, as well.
This also refactors AltId support to rely on the same mechanisms
as the IndexHeader class for indexing, user help, and
Xapian::QueryParser setup
