From: "Philip Oakley" <firstname.lastname@example.org> To: "Eric Wong" <email@example.com> Cc: <firstname.lastname@example.org> Subject: Re: Mapping old gmane numbers to existing amil servers? Date: Thu, 11 Aug 2016 22:00:48 +0100 Message-ID: <95848D06D55D4633A686DD892D12F501@PhilipOakley> (raw) In-Reply-To: <20160811075628.GA24690@starla> From: "Eric Wong" <email@example.com> Sent: Thursday, August 11, 2016 8:56 AM > Philip Oakley <firstname.lastname@example.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 index Thread overview: 5+ messages in thread (expand / mbox.gz / Atom feed / [top]) 2016-08-11 7:01 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 publically 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 to all the recipients using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=95848D06D55D4633A686DD892D12F501@PhilipOakley \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ /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
firstname.lastname@example.org mailing list mirror (one of many) Archives are clonable: git clone --mirror https://public-inbox.org/git git clone --mirror http://ou63pmih66umazou.onion/git git clone --mirror http://czquwvybam4bgbro.onion/git git clone --mirror http://hjrcffqmbrq6wope.onion/git Newsgroups are available over NNTP: nntp://news.public-inbox.org/inbox.comp.version-control.git nntp://ou63pmih66umazou.onion/inbox.comp.version-control.git nntp://czquwvybam4bgbro.onion/inbox.comp.version-control.git nntp://hjrcffqmbrq6wope.onion/inbox.comp.version-control.git nntp://news.gmane.org/gmane.comp.version-control.git note: .onion URLs require Tor: https://www.torproject.org/ or Tor2web: https://www.tor2web.org/ AGPL code for this site: git clone https://public-inbox.org/ public-inbox