unofficial mirror of meta@public-inbox.org
 help / color / mirror / Atom feed
From: Eric Wong <e@80x24.org>
To: meta@public-inbox.org
Subject: [PATCH 3/4] doc: extindex update on configuration and union section
Date: Wed, 15 Feb 2023 08:01:11 +0000	[thread overview]
Message-ID: <20230215080112.1740815-4-e@80x24.org> (raw)
In-Reply-To: <20230215080112.1740815-1-e@80x24.org>

The coderepo indexer will use similar ideas, I think...
---
 Documentation/public-inbox-extindex.pod | 10 +++++++---
 1 file changed, 7 insertions(+), 3 deletions(-)

diff --git a/Documentation/public-inbox-extindex.pod b/Documentation/public-inbox-extindex.pod
index f71a90e5..8370b905 100644
--- a/Documentation/public-inbox-extindex.pod
+++ b/Documentation/public-inbox-extindex.pod
@@ -77,9 +77,9 @@ L<public-inbox-extindex-format(5)>
 
 =head1 CONFIGURATION
 
-public-inbox-extindex does not currently write to the
-L<public-inbox-config(5)> file, configuration may be entered
-manually.  The extindex name of C<all> is a special case which
+public-inbox-extindex does not write to the L<public-inbox-config(5)>
+file, it must be entered manually.
+The extindex name of C<all> is a special case which
 corresponds to indexing C<--all> inboxes.  An example for
 C<--all> is as follows:
 
@@ -89,6 +89,10 @@ C<--all> is as follows:
 		coderepo = foo
 		coderepo = bar
 
+Putting an C<extindex> entry in the config allows L<PublicInbox::WWW>.
+You can have any number of C<extentry.$NAME> sections where C<$NAME>
+is something other than C<all> to display a union of several inboxes.
+
 See L<public-inbox-config(5)> for more details.
 
 =head1 ENVIRONMENT

  parent reply	other threads:[~2023-02-15  8:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-15  8:01 [PATCH 0/4] various doc updates Eric Wong
2023-02-15  8:01 ` [PATCH 1/4] doc: WWW + cgi: favor -netd over -httpd Eric Wong
2023-02-15  8:01 ` [PATCH 2/4] doc: flow: update with newer tools, note forkability Eric Wong
2023-02-15  8:01 ` Eric Wong [this message]
2023-02-15  8:01 ` [PATCH 4/4] Makefile.PL: drop update-copyrights rule Eric Wong

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=20230215080112.1740815-4-e@80x24.org \
    --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).