See L<public-inbox-init(1)/--jobs> for a full description
of sharding.
-C<--jobs=0> is accepted as of public-inbox 1.6.0 (PENDING)
+C<--jobs=0> is accepted as of public-inbox 1.6.0
to disable parallel indexing regardless of the number of
pre-existing shards.
it is possible to use this without C<--reindex>, it makes little
sense to do so.
-Available in public-inbox 1.6.0 (PENDING).
+Available in public-inbox 1.6.0+.
=item --prune
initial index and full C<--reindex> invocations (but not
incremental updates).
-Available in public-inbox 1.6.0 (PENDING).
+Available in public-inbox 1.6.0+.
=item --no-fsync
may even find disabling L<fdatasync(2)> causes too much dirty
data to accumulate, resulting on latency spikes from writeback.
-Available in public-inbox 1.6.0 (PENDING).
+Available in public-inbox 1.6.0+.
=item --sequential-shard
per-invocation basis. See L</publicinbox.indexSequentialShard>
below.
-Available in public-inbox 1.6.0 (PENDING).
+Available in public-inbox 1.6.0+.
=item --skip-docdata
See L<public-inbox-init(1)/--skip-docdata> for description and caveats.
-Available in public-inbox 1.6.0 (PENDING).
+Available in public-inbox 1.6.0+.
=back
search results, but it is otherwise non-fatal. Using C<--reindex>
will bring everything back up-to-date.
-Available in public-inbox 1.6.0 (PENDING).
+Available in public-inbox 1.6.0+.
This is ignored on L<public-inbox-v1-format(5)> inboxes.