It's pretty useful, I think. --- Documentation/lei-add-external.pod | 2 ++ Documentation/public-inbox-clone.pod | 5 +++++ 2 files changed, 7 insertions(+)
diff --git a/Documentation/lei-add-external.pod b/Documentation/lei-add-external.pod index 1ab65a1650a6..1761eed1ed78 100644 --- a/Documentation/lei-add-external.pod +++ b/Documentation/lei-add-external.pod @@ -29,6 +29,8 @@ Default: 0 =item --mirror=URL Create C<LOCATION> by mirroring the public-inbox at C<URL>. +C<LOCATION> will have a Makefile with a C<make update> +target to update the external. =item --epoch=RANGE diff --git a/Documentation/public-inbox-clone.pod b/Documentation/public-inbox-clone.pod index efee01eec592..103260913d92 100644 --- a/Documentation/public-inbox-clone.pod +++ b/Documentation/public-inbox-clone.pod @@ -18,6 +18,11 @@ L<public-inbox-index(1)>. Those commands must be run separately if serving/searching the mirror is required. As-is, public-inbox-clone is suitable for creating a git-only backup. +public-inbox-clone creates a Makefile with handy targets to update the +inbox once indexed. This Makefile may be edited by the user; it will +not be rewritten by L<public-inbox-fetch(1)> unless it is removed +completely. + public-inbox-clone does not use nor require any extra configuration files (not even C<~/.public-inbox/config>). -- unsubscribe: one-click, see List-Unsubscribe header archive: https://public-inbox.org/meta/
