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
