Johannes Schindelin [off-list ref] wrote:

Hi Eric,

On Thu, 28 Nov 2019, Eric Wong wrote:

quoted

Johannes Schindelin [off-list ref] wrote:

quoted

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...