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 22:31:45 +0000 [thread overview]
Message-ID: <20191128223145.GA23772@dcvr> (raw)
In-Reply-To: <nycvar.QRO.7.76.6.1911282315570.31080@tvgsbejvaqbjf.bet>
Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:
> Hi Eric,
>
> On Thu, 28 Nov 2019, Eric Wong wrote:
>
> > Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:
> >
> > > 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"
>
> I just had a look at its contents:
>
> -- snip --
> ; example public-inbox config snippet for "git"
> ; see public-inbox-config(5) manpage for more details:
> ; https://public-inbox.org/public-inbox-config.html
> [publicinbox "git"]
> inboxdir = /path/to/top-level-inbox
> ; note: public-inbox before v1.2.0 used "mainrepo"
> ; instead of "inboxdir", both remain supported after 1.2
> mainrepo = /path/to/top-level-inbox
> address = git@vger.kernel.org
> listid = git.vger.kernel.org
> filter = PublicInbox::Filter::Mirror
> newsgroup = org.kernel.vger.git
> nntpmirror = nntp://nntp.lore.kernel.org/org.kernel.vger.git
> -- snap --
>
> Isn't `inboxdir` and `mainrepo` incorrect?
How so? It's fine to have both in case users need to downgrade
to older versions of public-inbox.
> And yes, adding `epoch` information there would be very welcome.
Noted. Not sure if the "modified" and "fingerprint" keys of
manifest would make sense there, too...
next prev parent reply other threads:[~2019-11-28 22:31 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
2019-11-28 22:17 ` Johannes Schindelin
2019-11-28 22:31 ` Eric Wong [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20191128223145.GA23772@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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.