From: Eric Wong <e@80x24.org>
To: meta@public-inbox.org
Subject: [PATCH 5/5] doc: clone: document --remote-manifest= option
Date: Mon, 13 Mar 2023 12:00:24 +0000 [thread overview]
Message-ID: <20230313120024.1911925-6-e@80x24.org> (raw)
In-Reply-To: <20230313120024.1911925-1-e@80x24.org>
---
Documentation/public-inbox-clone.pod | 11 +++++++++++
1 file changed, 11 insertions(+)
diff --git a/Documentation/public-inbox-clone.pod b/Documentation/public-inbox-clone.pod
index af4e8e95..90359f5a 100644
--- a/Documentation/public-inbox-clone.pod
+++ b/Documentation/public-inbox-clone.pod
@@ -129,6 +129,17 @@ is specified where C<FILE> is an empty string (C<"">), then C<manifest.js.gz>
This is a new option in public-inbox 2.0+
+=item --remote-manifest=URL|RELATIVE_PATH
+
+Use an alternate location for the remote manifest.js.gz file.
+This mah be specified as a full absolute URL (e.g
+C<--remote-manifest=https://80x24.org/lore/pub/manifest.js.gz>),
+or a pathname relative to the ROOT_URL (e.g
+C<--remote-manifest=pub/manifest.js.gz> when ROOT_URL is
+C<https://80x24.org/lore/>
+
+This is a new option in public-inbox 2.0+
+
=item --project-list=FILE
When cloning code repos from a manifest, generate a cgit-compatible
next prev parent reply other threads:[~2023-03-13 12:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-13 12:00 [PATCH 0/5] clone improvements Eric Wong
2023-03-13 12:00 ` [PATCH 1/5] lei_mirror: describe why the {ibx} field is used Eric Wong
2023-03-13 12:00 ` [PATCH 2/5] lei_mirror: do not re-fetch inbox.config.example Eric Wong
2023-03-13 12:00 ` [PATCH 3/5] lei_mirror: do not fetch to read-only directories Eric Wong
2023-03-13 12:00 ` [PATCH 4/5] lei_mirror: handle UTF-8 from manifest.js.gz properly Eric Wong
2023-03-13 12:00 ` Eric Wong [this message]
2023-03-13 23:34 ` [PATCH 5/5] doc: clone: document --remote-manifest= option Kyle Meyer
2023-03-14 20:50 ` [PATCH] doc: clone: fix typo in --remote-manifest= description 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=20230313120024.1911925-6-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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/public-inbox.git
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).