From: "Clément Pit-Claudel" <cpitclaudel@gmail.com>
To: emacs-devel@gnu.org
Subject: Re: TLS certificate on elpa.gnu.org
Date: Sun, 4 Feb 2018 10:23:16 -0500 [thread overview]
Message-ID: <488775a0-3cdd-244a-b3f1-48775b3c37e5@gmail.com> (raw)
In-Reply-To: <314F38A2-9B19-46C2-809A-FAFB5B5EC822@gmail.com>
On 2018-02-03 22:13, Neil Okamoto wrote:
> Which means tools like “Cask” which invoke Emacs in batch to install dependencies from package repos like ELPA or MELPA are failing on the Travis CI infrastructure.
Ah, thanks so much for tracking this down! I'd been wanting to track that error down for a while. Great sleuthing work!
next prev parent reply other threads:[~2018-02-04 15:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-04 3:13 TLS certificate on elpa.gnu.org Neil Okamoto
2018-02-04 15:23 ` Clément Pit-Claudel [this message]
2018-02-04 16:29 ` Eli Zaretskii
2018-02-04 16:48 ` Philipp Stephani
2018-02-04 17:51 ` Eli Zaretskii
2018-02-04 20:11 ` Neil Okamoto
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: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=488775a0-3cdd-244a-b3f1-48775b3c37e5@gmail.com \
--to=cpitclaudel@gmail.com \
--cc=emacs-devel@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 public inbox
https://git.savannah.gnu.org/cgit/emacs.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).