unofficial mirror of meta@public-inbox.org
 help / color / mirror / Atom feed
From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: Eric Wong <e@80x24.org>
Cc: meta@public-inbox.org
Subject: Re: [PATCH 00/11] indexheader + altid enhancements
Date: Mon, 12 Aug 2024 09:55:32 -0400	[thread overview]
Message-ID: <20240812-eccentric-hypersonic-fossa-7b9c1e@lemur> (raw)
In-Reply-To: <20240810090012.23269-1-e@80x24.org>

On Sat, Aug 10, 2024 at 09:00:01AM GMT, Eric Wong wrote:
> The indexheader feature allows arbitrary headers to be indexed.
> This can be done with both per-inbox Xapian indices and extindex
> spanning multiple inboxes.

Nice! I will try this out shortly and let you know how it's looking.

-K

      parent reply	other threads:[~2024-08-12 14:03 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-10  9:00 [PATCH 00/11] indexheader + altid enhancements Eric Wong
2024-08-10  9:00 ` [PATCH 01/11] search: support per-inbox indexheader directive Eric Wong
2024-08-10  9:00 ` [PATCH 02/11] indexheader: deduplicate common values Eric Wong
2024-08-10  9:00 ` [PATCH 03/11] search: help: avoid ':' in user prefixes Eric Wong
2024-08-10  9:00 ` [PATCH 04/11] search: move QueryParser mappings to xh_args Eric Wong
2024-08-10  9:00 ` [PATCH 05/11] www_text: show indexheader contents in help Eric Wong
2024-08-10  9:00 ` [PATCH 06/11] www: don't memoize ->user_help contents Eric Wong
2024-08-10  9:00 ` [PATCH 07/11] extindex: avoid branch in ->index_eml Eric Wong
2024-08-10  9:00 ` [PATCH 08/11] t/extsearch: use autodie to detect chmod failures Eric Wong
2024-08-10  9:00 ` [PATCH 09/11] t/extsearch: use xsys_e to detect errors Eric Wong
2024-08-10  9:00 ` [PATCH 10/11] extindex: support extindex.*.indexheader Eric Wong
2024-08-10  9:00 ` [PATCH 11/11] extindex: support per-inbox indexheader+altid Eric Wong
2024-08-12 13:55 ` Konstantin Ryabitsev [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=20240812-eccentric-hypersonic-fossa-7b9c1e@lemur \
    --to=konstantin@linuxfoundation.org \
    --cc=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).