From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: GNU Elpa not reachable (possibly OT)
Date: Tue, 19 Feb 2019 05:37:51 +0200 [thread overview]
Message-ID: <8336okjvn4.fsf@gnu.org> (raw)
In-Reply-To: <20190218170906678696564@bob.proulx.com> (message from Bob Proulx on Mon, 18 Feb 2019 17:17:12 -0700)
> Date: Mon, 18 Feb 2019 17:17:12 -0700
> From: Bob Proulx <bob@proulx.com>
>
> Eli Zaretskii wrote:
> > Joost Kremers wrote:
> > > PING elpa.gnu.org(2001:470:142:5::89 (2001:470:142:5::89)) 56 data
> > > bytes
> > > >From 2001:470:142::1 (2001:470:142::1) icmp_seq=1 Destination
> > > unreachable: Address unreachable
> >
> > Write to savannah-hackers-public@gnu.org with these details.
>
> The Savannah folks are a different set from the Emacs ELPA folks.
> Although Ian, one of the FSF admins, is subscribed and therefore
> perhaps he might jump in. But talking to the Emacs ELPA folks
> directly would be more direct. I don't know who they are.
Not sure what you mean. ELPA is hosted on Savannah, it's a Git
repository, and the problem sounds like connectivity problem with
IPv6, so savannah-hackers-public sounds appropriate to me.
next prev parent reply other threads:[~2019-02-19 3:37 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-18 14:58 GNU Elpa not reachable (possibly OT) Joost Kremers
2019-02-18 16:19 ` Eli Zaretskii
2019-02-18 21:10 ` Joost Kremers
2019-02-19 0:17 ` Bob Proulx
2019-02-19 3:37 ` Eli Zaretskii [this message]
2019-02-19 5:07 ` Bob Proulx
2019-02-19 16:05 ` Eli Zaretskii
2019-02-19 16:59 ` Joost Kremers
2019-02-19 17:05 ` Bob Proulx
2019-02-19 17:27 ` Eli Zaretskii
2019-02-20 9:10 ` Joost Kremers
2019-02-18 17:08 ` Robert Pluim
2019-02-18 18:19 ` Robert Pluim
2019-02-19 17:03 ` Joost Kremers
2019-02-19 19:08 ` Robert Pluim
2019-02-20 9:42 ` Joost Kremers
2019-02-20 10:15 ` Robert Pluim
2019-03-01 7:27 ` Joost Kremers
2019-03-01 10:02 ` Robert Pluim
2019-03-01 21:06 ` Jude DaShiell
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8336okjvn4.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=help-gnu-emacs@gnu.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.