From: Eric Wong <e@80x24.org>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Jeff King <peff@peff.net>,
Konstantin Ryabitsev <konstantin@linuxfoundation.org>,
git@vger.kernel.org
Subject: Re: [PATCH 1/2] doc: recommend lore.kernel.org over public-inbox.org
Date: Thu, 28 Nov 2019 19:48:29 +0000 [thread overview]
Message-ID: <20191128194829.GA15521@dcvr> (raw)
In-Reply-To: <nycvar.QRO.7.76.6.1911281123100.31080@tvgsbejvaqbjf.bet>
Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:
> On Wed, 27 Nov 2019, Eric Wong wrote:
> > The "0" is the "epoch", and larger repos have multiple epochs,
> > roughly 1GB each. https://lore.kernel.org/lkml/ has 0..7, right now.
>
> Okay, so how does that work, is the idea that you should graft them
> together using replacement objects if you want to have the full archive?
Yes. Except we don't actually use grafts/replace and users can
currently only clone the latest epoch of LKML. In the future,
it should also be easy to jettison old epochs if space is
limited.
> And: if I want to track the latest mails in GitGitGadget, what indication
> will I have that I'll need to switch to `.../1`?
You can use the gzipped JSON grokmirror manifest at:
https://lore.kernel.org/git/manifest.js.gz
grokmirror could be a bit of a pain to install because of Python
dependencies, so periodically attempting to clone the next
numbered epoch ought to be fine, too.
I've also considered adding epoch info into
https://lore.kernel.org/git/_/text/config/raw
so shell scripters w/o JSON parsers can use "git config"
next prev parent reply other threads:[~2019-11-28 19:48 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-20 15:43 This list is now also archived on lore.kernel.org/git Konstantin Ryabitsev
2019-11-20 19:55 ` Eric Wong
2019-11-27 15:31 ` Ævar Arnfjörð Bjarmason
2019-11-27 16:18 ` Jeff King
2019-11-27 20:25 ` Eric Wong
2019-11-27 12:52 ` Jeff King
2019-11-27 12:53 ` [PATCH 1/2] doc: recommend lore.kernel.org over public-inbox.org Jeff King
2019-11-27 12:59 ` Eric Wong
2019-11-27 20:00 ` Johannes Schindelin
2019-11-27 20:04 ` Eric Wong
2019-11-28 10:25 ` Johannes Schindelin
2019-11-28 19:48 ` Eric Wong [this message]
2019-11-28 22:17 ` Johannes Schindelin
2019-11-28 22:31 ` Eric Wong
2019-11-29 9:32 ` Johannes Schindelin
2019-11-29 9:59 ` Eric Wong
2019-11-27 12:54 ` [PATCH 2/2] doc: replace public-inbox links with lore.kernel.org Jeff King
2019-11-27 14:37 ` Derrick Stolee
2019-11-27 19:28 ` [PATCH 0/2] Hi Peff, Denton Liu
2019-11-27 19:28 ` [PATCH 1/2] doc: replace MARC links with LKML Denton Liu
2019-11-27 19:28 ` [PATCH 2/2] RelNotes: replace Gmane with real Message-IDs Denton Liu
2019-11-28 0:16 ` Denton Liu
2019-11-30 17:14 ` [PATCH 0/2] Hi Peff, Junio C Hamano
2019-12-02 19:26 ` [PATCH v2 0/3] Doc: replace opaque mail archive links with lore.kernel.org Denton Liu
2019-12-02 19:26 ` [PATCH v2 1/3] doc: replace MARC " Denton Liu
2019-12-02 19:26 ` [PATCH v2 2/3] RelNotes: replace Gmane with real Message-IDs Denton Liu
2019-12-02 19:26 ` [PATCH v2 3/3] doc: replace LKML link with lore.kernel.org Denton Liu
2019-12-04 18:28 ` [PATCH v2 0/3] Doc: replace opaque mail archive links " Junio C Hamano
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: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20191128194829.GA15521@dcvr \
--to=e@80x24.org \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=konstantin@linuxfoundation.org \
--cc=peff@peff.net \
/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/mirrors/git.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).