From: Eric Wong <e@80x24.org>
To: Jeff King <peff@peff.net>
Cc: Johannes Schindelin <Johannes.Schindelin@gmx.de>, git@vger.kernel.org
Subject: Re: Thank you for public-inbox!
Date: Wed, 29 Aug 2018 10:02:43 +0000 [thread overview]
Message-ID: <20180829100243.GA28180@dcvr> (raw)
In-Reply-To: <20180829050745.GD15274@sigill.intra.peff.net>
Jeff King <peff@peff.net> wrote:
> I've thought about mirroring it to a public server as well, just for
> redundancy. But without the same domain, I'm not sure it would be all
> that useful as a community resource.
I wouldn't get too attached to the domain, "public-inbox.org" is
too long for my tastes anyways. "peff.net/git/$MESSAGE_ID"
would actually be more user-friendly :>
A generic Message-ID redirection/finding service would be good,
(maybe some DHT thing, but... has that taken off for git blobs, yet?)
Anyways I hope to teach public-inbox to auto-linkify Message-ID-looking
strings "<XXXXXXXXXXX@XXXXXXXX>" into URLs for domain-portability,
(but it's ambiguous with email addresses). But yeah, I don't
like things being tied to domain names.
I've also been considering setting up a parallel instance
on 80x24.org to use the more-scalable "v2" repository format
developed for https://lore.kernel.org/lkml/
Speaking of lore, Konstantin confirmed he'll be getting more
vger lists up: https://public-inbox.org/meta/20180827205811.GA1611@chatter
next prev parent reply other threads:[~2018-08-29 10:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-27 14:25 Thank you for public-inbox! Johannes Schindelin
2018-08-27 17:31 ` Eric Wong
2018-08-29 5:07 ` Jeff King
2018-08-29 10:02 ` Eric Wong [this message]
2018-08-29 15:43 ` Andrei Rybak
2018-08-29 16:30 ` Ævar Arnfjörð Bjarmason
2018-08-30 3:30 ` Jeff King
2018-08-30 3:56 ` Jonathan Nieder
2018-08-30 7:20 ` Eric Wong
2018-08-31 1:14 ` Jonathan Nieder
2018-08-31 11:01 ` Eric Wong
2018-08-30 7:20 ` Eric Wong
2018-08-30 8:19 ` Jeff King
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=20180829100243.GA28180@dcvr \
--to=e@80x24.org \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.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).