From: Ted Zlatanov <tzz@lifelogs.com>
To: emacs-devel@gnu.org
Subject: Re: proposal: require GnuTLS 3.1.x (previous stable)
Date: Wed, 26 Nov 2014 16:18:26 -0500 [thread overview]
Message-ID: <87egsp8xul.fsf@lifelogs.com> (raw)
In-Reply-To: 87oartaoq7.fsf@lifelogs.com
On Wed, 26 Nov 2014 11:52:32 -0500 Ted Zlatanov <tzz@lifelogs.com> wrote:
TZ> On Wed, 26 Nov 2014 10:42:37 -0500 Stefan Monnier <monnier@IRO.UMontreal.CA> wrote:
SM> We usually consider it OK to drop support for things that are "older
SM> than Debian stable" or thereabout. But usually it depends a lot on the
SM> cost of maintaining this backward compatibility. In this case, the cost
SM> seems to be very reasonable, so I see no reason to drop support for
SM> GnuTLS2 at this stage. Those tradeoffs change over time, so by Emacs-26
SM> it's quite likely that we'll get rid of GnuTLS2 support, indeed.
TZ> OK, so let's reevaluate then. For now we'll continue supporting the 2.x
TZ> versions we do now. It would be extremely helpful to have an easy way
TZ> to test Emacs compilation and functionality with ERT, perhaps in a
TZ> Vagrantfile or in Hydra or Travis or whatever.
FWIW, I just got a note about this on gnutls-devel that strongly
suggests supporting GnuTLS 3.x only:
http://permalink.gmane.org/gmane.comp.encryption.gpg.gnutls.devel/7811
I don't know if it changes anyone's mind :)
Ted
next prev parent reply other threads:[~2014-11-26 21:18 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-23 18:38 Build failure (master; MS-Windows) Dani Moncayo
2014-11-23 21:41 ` Dani Moncayo
2014-11-23 22:07 ` Lars Magne Ingebrigtsen
2014-11-23 22:52 ` Dani Moncayo
2014-11-23 22:57 ` Lars Magne Ingebrigtsen
2014-11-23 23:09 ` Dani Moncayo
2014-11-25 9:32 ` proposal: require GnuTLS 3.1.x (previous stable) (was: Build failure (master; MS-Windows)) Ted Zlatanov
2014-11-25 15:57 ` proposal: require GnuTLS 3.1.x (previous stable) Lars Magne Ingebrigtsen
2014-11-25 16:28 ` Ted Zlatanov
2014-11-25 16:38 ` Buildbot for Emacs? (was: proposal: require GnuTLS 3.1.x (previous stable)) Lars Magne Ingebrigtsen
2014-11-25 16:50 ` Buildbot for Emacs? Glenn Morris
2014-11-25 16:55 ` Ted Zlatanov
2014-11-25 22:15 ` Glenn Morris
2014-11-25 23:12 ` Ted Zlatanov
2014-11-26 9:52 ` Tom
2014-11-25 17:05 ` Lars Magne Ingebrigtsen
2014-11-25 22:14 ` Glenn Morris
2014-11-25 17:34 ` proposal: require GnuTLS 3.1.x (previous stable) Stefan Monnier
2014-11-25 18:55 ` Ivan Shmakov
2014-11-26 9:14 ` Peder O. Klingenberg
2014-11-26 12:57 ` Ivan Shmakov
2014-11-26 13:47 ` Peder O. Klingenberg
2014-11-26 13:08 ` Ted Zlatanov
2014-11-26 14:12 ` Peder O. Klingenberg
2014-11-26 15:42 ` Stefan Monnier
2014-11-26 16:52 ` Ted Zlatanov
2014-11-26 21:18 ` Ted Zlatanov [this message]
2014-11-26 21:37 ` Lars Magne Ingebrigtsen
2014-11-27 2:13 ` Stefan Monnier
2014-11-27 2:33 ` Ted Zlatanov
2014-11-28 18:51 ` Ted Zlatanov
2014-11-28 19:31 ` Stefan Monnier
2014-11-29 20:02 ` Glenn Morris
2014-11-26 13:46 ` Michael Welsh Duggan
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=87egsp8xul.fsf@lifelogs.com \
--to=tzz@lifelogs.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).