From: "Philip Oakley" <philipoakley@iee.org>
To: "Eric Wong" <e@80x24.org>
Cc: <git@vger.kernel.org>
Subject: Re: Mapping old gmane numbers to existing amil servers?
Date: Thu, 11 Aug 2016 22:00:48 +0100 [thread overview]
Message-ID: <95848D06D55D4633A686DD892D12F501@PhilipOakley> (raw)
In-Reply-To: 20160811075628.GA24690@starla
From: "Eric Wong" <e@80x24.org>
Sent: Thursday, August 11, 2016 8:56 AM
> Philip Oakley <philipoakley@iee.org> wrote:
>> Is there an accessible mapping from the old gmane message numbers to one
>> of
>> the remaining email list servers for the git list?
>
> Yes, I just posted about this after posting an initial mapping
> a few weeks ago:
> https://public-inbox.org/git/20160811002819.GA8311@starla/T/#u
>
> Using "gmane:$NUM" in the search bar should work, now.
> (there's a few missing messages which might've been due to
> off-by-one errors, will fill them in soon)
>
>> I've seen discussions about the public-inbox, but no mention of any
>> mapping
>> for old message references.
>
> I had a gzipped text file published originally if you look
> upthread there.
>
Thanks.
The raw download works. My home ISP is currently blocking your email for
some reason, though I do see it at my work - my iee.org alias is via my
professional body which duplicates the email when it relays it.
On thing I did note on the web display of the threads is that it would be
good to have a leader of " . . . . . `" so that one can count the level of
indent, and see the alignments via the columns of dots.
When looking at
https://public-inbox.org/git/0648000B273C412AB7140AE959EBC99A%40PhilipOakley/ I
had difficulty working out which email the last 4 were replying to.
next prev parent reply other threads:[~2016-08-11 21:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-11 7:01 Mapping old gmane numbers to existing amil servers? Philip Oakley
2016-08-11 7:56 ` Eric Wong
2016-08-11 21:00 ` Philip Oakley [this message]
2016-08-11 22:26 ` Eric Wong
2016-08-12 7:38 ` Philip Oakley
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=95848D06D55D4633A686DD892D12F501@PhilipOakley \
--to=philipoakley@iee.org \
--cc=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).