From: Eric Wong <e@80x24.org>
To: git@vger.kernel.org
Subject: Re: This list is now also archived on lore.kernel.org/git
Date: Wed, 20 Nov 2019 19:55:56 +0000 [thread overview]
Message-ID: <20191120195556.GA25189@dcvr> (raw)
In-Reply-To: <20191120154347.x6w4v7cdzy4yrx6q@chatter.i7.local>
Konstantin Ryabitsev <konstantin@linuxfoundation.org> wrote:
> Hi, all:
>
> I used Eric's public-inbox.org archives to set up our own copy on
> lore.kernel.org and identical list archives are now available on that
> server.
Almost :) I forget it exists, but there's the "gmane:$ARTICLE_NUM"
altid mapping search support on my server for legacy gmane URLs.
Instructions to set it up:
https://public-inbox.org/meta/20160811002348.9719-1-e@80x24.org/
> I spoke with Eric and he recommends that official project documentation
> starts using lore.kernel.org/git URLs in daily use and git's official
> documentation in order to allow him more freedom of decision when it
> comes to hosting his equipment. The URLs at both domains remain the
> same, e.g.:
Yup, .org TLD renewal costs will likely go up and I won't pay
higher costs to keep .org domains.
The system running public-inbox.org (and the recommended
onions(*)) will stay running and will have bleeding edge
code on it.
* Accessible via Tor, no need to depend on registrars:
http://hjrcffqmbrq6wope.onion/
http://ou63pmih66umazou.onion/
http://czquwvybam4bgbro.onion/
next prev parent reply other threads:[~2019-11-20 19:55 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 [this message]
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
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=20191120195556.GA25189@dcvr \
--to=e@80x24.org \
--cc=git@vger.kernel.org \
/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).