From: Noam Postavsky <npostavs@gmail.com>
To: David Engster <deng@randomsample.de>
Cc: Chris Marusich <cmmarusich@gmail.com>,
ding@gnus.org, gnutls-help@lists.gnutls.org
Subject: Re: TLS v1.3 - Gnus and GnuTLS - Client resets connection
Date: Thu, 8 Aug 2019 08:02:33 -0400 [thread overview]
Message-ID: <CAM-tV--NmwivmgSmcUgFs-G-aCtnHJj5Kmimesn=xPOXiVpgDQ@mail.gmail.com> (raw)
In-Reply-To: <87v9v8rnih.fsf@randomsample>
On Thu, 8 Aug 2019 at 07:08, David Engster <deng@randomsample.de> wrote:
> https://debbugs.gnu.org/cgi/bugreport.cgi?bug=34341
>
> This will be fixed in Emacs 27 (or maybe another Emacs 26 point
> release, whichever comes first).
26.3 will come first; it should already be fixed in the 26.2.90 pretest.
next prev parent reply other threads:[~2019-08-08 12:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-08 8:51 Chris Marusich
2019-08-08 9:53 ` David Engster
2019-08-08 12:02 ` Noam Postavsky [this message]
2019-08-08 16:04 ` Chris Marusich
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='CAM-tV--NmwivmgSmcUgFs-G-aCtnHJj5Kmimesn=xPOXiVpgDQ@mail.gmail.com' \
--to=npostavs@gmail.com \
--cc=cmmarusich@gmail.com \
--cc=deng@randomsample.de \
--cc=ding@gnus.org \
--cc=gnutls-help@lists.gnutls.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.
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 NNTP newsgroup(s).