From: Eric Wong <e@80x24.org>
To: meta@public-inbox.org
Subject: Re: [PATCH] search: support per-inbox indexheader directive
Date: Wed, 8 May 2024 11:32:52 +0000 [thread overview]
Message-ID: <20240508113252.M354058@dcvr> (raw)
In-Reply-To: <20240508110957.3108196-1-e@80x24.org>
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...
prev parent reply other threads:[~2024-05-08 11:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-08 11:09 [PATCH] search: support per-inbox indexheader directive Eric Wong
2024-05-08 11:32 ` 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=20240508113252.M354058@dcvr \
--to=e@80x24.org \
--cc=meta@public-inbox.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).