I forgot to document these when I implemented them :x --- Documentation/public-inbox-clone.pod | 21 +++++++++++++++++++++ 1 file changed, 21 insertions(+)
diff --git a/Documentation/public-inbox-clone.pod b/Documentation/public-inbox-clone.pod index 2a7081ac..53acf356 100644 --- a/Documentation/public-inbox-clone.pod +++ b/Documentation/public-inbox-clone.pod @@ -108,6 +108,27 @@ as relative to the C<DESTINATION> directory. If only C<--manifest=> is specified where C<FILE> is an empty string (C<"">), then C<manifest.js.gz> (C<$DESTINATION/manifest.js.gz>) is the implied value of C<FILE>. +=item --project-list=FILE + +When cloning code repos from a manifest, generate a cgit-compatible +project list. + +If C<FILE> does not start with C</>, C<./>, or C<../>, it is treated +as relative to the C<DESTINATION> directory. If only C<--project-list=> +is specified where C<FILE> is an empty string (C<"">), then C<projects.list> +(C<$DESTINATION/projects.list>) is the implied value of C<FILE>. + +=item --post-update-hook=COMMAND + +Hooks to run after a repository is cloned or updated, C<COMMAND> will +have the bare git repository destination given as its first and only +argument. + +For v2 inboxes, this operates on a per-epoch basis. + +May be specified multiple times to run multiple commands in the +order specified on the command-line. + =item -p =item --prune
