user/dev discussion of public-inbox itself
 help / color / mirror / code / Atom feed
From: "Eric Wong (Contractor, The Linux Foundation)" <e@80x24.org>
To: meta@public-inbox.org
Subject: [PATCH 0/4] grokmirror-compatible manifests
Date: Sun,  9 Jun 2019 04:31:01 +0000	[thread overview]
Message-ID: <20190609043105.22338-1-e@80x24.org> (raw)

Maintaining mirrors is a pain, especially for v2 repos
and multiple epochs.  So support both per-domain matching
and per-inbox manifests which can be fed to grok-pull(1)

https://git.kernel.org/pub/scm/utils/grokmirror/grokmirror.git

Eric Wong (Contractor, The Linux Foundation) (4):
  wwwlisting: allow hiding entries from manifest
  wwwlisting: generate grokmirror-compatible manifest.js.gz
  www: wire up /$INBOX/manifest.js.gz, too
  www: support $INBOX/git/$EPOCH.git for v2 cloning

 MANIFEST                      |   1 +
 lib/PublicInbox/WWW.pm        |  17 +++-
 lib/PublicInbox/WwwListing.pm | 174 +++++++++++++++++++++++++++++-----
 t/psgi_v2.t                   |   2 +
 t/v2mirror.t                  |   8 +-
 t/www_listing.t               | 158 ++++++++++++++++++++++++++++++
 6 files changed, 330 insertions(+), 30 deletions(-)
 create mode 100644 t/www_listing.t

-- 
EW

             reply	other threads:[~2019-06-09  4:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-09  4:31 Eric Wong (Contractor, The Linux Foundation) [this message]
2019-06-09  4:31 ` [PATCH 1/4] wwwlisting: allow hiding entries from manifest Eric Wong (Contractor, The Linux Foundation)
2019-06-09  4:31 ` [PATCH 2/4] wwwlisting: generate grokmirror-compatible manifest.js.gz Eric Wong (Contractor, The Linux Foundation)
2019-06-09  4:31 ` [PATCH 3/4] www: wire up /$INBOX/manifest.js.gz, too Eric Wong (Contractor, The Linux Foundation)
2019-06-09  4:31 ` [PATCH 4/4] www: support $INBOX/git/$EPOCH.git for v2 cloning Eric Wong (Contractor, The Linux Foundation)
2019-06-10  6:21 ` [PATCH 5/4] git: ensure ->modified returns an integer Eric Wong (Contractor, The Linux Foundation)

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=20190609043105.22338-1-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).