all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Eric Hanchrow <eric.hanchrow@gmail.com>
Cc: 31313@debbugs.gnu.org
Subject: bug#31313: 26.1; gnutls.c: [0] (Emacs) Received alert: Handshake failed
Date: Mon, 30 Apr 2018 05:34:28 +0300	[thread overview]
Message-ID: <83lgd5s9qj.fsf@gnu.org> (raw)
In-Reply-To: <CAHZoxq-DD5CaDUUZSmQgvd5YyUAxkMtpZ75fCyAUyFcdcYr0Tg@mail.gmail.com> (message from Eric Hanchrow on Sun, 29 Apr 2018 19:59:19 +0000)

> From: Eric Hanchrow <eric.hanchrow@gmail.com>
> Date: Sun, 29 Apr 2018 19:59:19 +0000
> 
> This used to work until perhaps a few days or weeks ago; as far as I
> know nothing has changed.
> 
> 
> In GNU Emacs 26.1 (build 1, x86_64-pc-linux-gnu)
>   of 2018-04-29 built on ip-10-0-0-79
> Repository revision: c18ec6afc0ee7fa2ad5831fbd3a51ca4df3c35b7

Is this Emacs 26.1 RC1, or is it something else?  You are saying it
worked until a few days ago, but it isn't clear whether your Emacs
changed since then.  And there's no commit with the above SHA1 in the
Emacs repository, AFAICT.  So I'm unsure what codebase you are using
and how to interpret the fact that it used to work not long ago.





  parent reply	other threads:[~2018-04-30  2:34 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-29 19:59 bug#31313: 26.1; gnutls.c: [0] (Emacs) Received alert: Handshake failed Eric Hanchrow
2018-04-29 20:38 ` Noam Postavsky
2018-04-29 21:01 ` Noam Postavsky
2018-04-29 22:32 ` Noam Postavsky
2018-04-30  2:34 ` Eli Zaretskii [this message]
2018-04-30  5:26   ` Eli Zaretskii
2018-05-02  2:47     ` Eric Hanchrow
2018-05-02 14:53       ` Eli Zaretskii
2018-05-03  3:24         ` Eric Hanchrow
2018-05-03 17:43           ` Eli Zaretskii
2018-05-04 22:49             ` Eric Hanchrow
2018-05-05  6:39               ` Eli Zaretskii
     [not found]   ` <CAHZoxq-_BUSvfaEbysKnvFN2tFpU+HhhFyR6G73Z6iKDXtOuTQ@mail.gmail.com>
2018-04-30 14:26     ` Eli Zaretskii

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=83lgd5s9qj.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=31313@debbugs.gnu.org \
    --cc=eric.hanchrow@gmail.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
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.