git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Eric Wong <e@80x24.org>
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 11:25:09 +0100 (CET)	[thread overview]
Message-ID: <nycvar.QRO.7.76.6.1911281123100.31080@tvgsbejvaqbjf.bet> (raw)
In-Reply-To: <20191127200421.GA27456@dcvr>

Hi,

On Wed, 27 Nov 2019, Eric Wong wrote:

> Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:
> > On Wed, 27 Nov 2019, Eric Wong wrote:
> > > Jeff King <peff@peff.net> wrote:
> > > > Since lore.kernel.org now has the same archive as public-inbox.org and
> > > > may have more longevity going forward[1], let's recommend people use it
> > > > for finding or referencing messages.
> > > >
> > > > [1] https://public-inbox.org/git/20191120195556.GA25189@dcvr/
> > > >       or if you like:
> > > >     https://lore.kernel.org/git/20191120195556.GA25189@dcvr/
> >
> > One of the things I appreciate most about https://public-inbox.org/git is
> > that you can clone it. I just tried this with
> > https://lore.kernel.org/git/...
> >
> > $ git clone https://lore.kernel.org/git/  lore-git
> > Cloning into 'lore-git'...
> > warning: You appear to have cloned an empty repository.
>
> Oops, that's a usability issue I hope to fix at some point.

That would be nice. As you can tell from my puzzlement, not everybody
scrolls down to the instruction (which I finally found after your
comment)...

:-D

> > Is this something other people also care about?
>
> Instructions are actually at the bottom:
>
>    git clone --mirror https://lore.kernel.org/git/0 git/git/0.git
>
> 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?

And: if I want to track the latest mails in GitGitGadget, what indication
will I have that I'll need to switch to `.../1`?

Thanks,
Dscho

  reply	other threads:[~2019-11-28 10:25 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 [this message]
2019-11-28 19:48             ` Eric Wong
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=nycvar.QRO.7.76.6.1911281123100.31080@tvgsbejvaqbjf.bet \
    --to=johannes.schindelin@gmx.de \
    --cc=e@80x24.org \
    --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).