unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Andy Moreton <andrewjmoreton@gmail.com>,
	Noam Postavsky <npostavs@users.sourceforge.net>,
	wingo@igalia.com, 25061@debbugs.gnu.org, ludo@gnu.org,
	p.stephani2@gmail.com, michael.albinus@gmx.de, larsi@gnus.org
Subject: bug#25061: consider adding %COMPAT to default gnutls priority string
Date: Wed, 20 Dec 2017 20:15:48 -0500	[thread overview]
Message-ID: <87a7ycj2yj.fsf@lifelogs.com> (raw)
In-Reply-To: <83lghxnzi9.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 20 Dec 2017 18:19:10 +0200")

On Wed, 20 Dec 2017 18:19:10 +0200 Eli Zaretskii <eliz@gnu.org> wrote: 

EZ> Thanks, but this means Emacs will now refuse to load GnuTLS on systems
EZ> that have version 3.4 or older of the library, right?  If so, I think
EZ> the loading and the use of the function should be conditioned by an
EZ> appropriate preprocessor directive to compile that code only for
EZ> 3.5.X.

I've applied Andy's updated patch for GnuTLS 3.5.1 and older, and
hard-coded compatibility for %DUMBFW between 3.2.5 when it was
introduced and 3.5.1.

Looking forward to closing this one for good... thanks.

Ted





  parent reply	other threads:[~2017-12-21  1:15 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-29 10:24 bug#25061: consider adding %COMPAT to default gnutls priority string Andy Wingo
2016-12-01 18:32 ` Ted Zlatanov
2016-12-01 20:25   ` Ludovic Courtès
2016-12-01 21:44     ` Ted Zlatanov
2017-01-24 22:48       ` Lars Ingebrigtsen
2017-01-30  8:01         ` Ludovic Courtès
2017-02-10 15:51           ` Andy Wingo
2017-02-13 16:04             ` Ted Zlatanov
2017-09-02 13:49               ` Eli Zaretskii
2017-09-06 19:32                 ` Ted Zlatanov
2017-09-07  7:18                   ` Michael Albinus
2017-09-14 21:11                     ` Ted Zlatanov
2017-09-15  6:05                       ` Eli Zaretskii
2017-12-02 17:36                         ` Eli Zaretskii
2017-12-09 23:50                           ` Ted Zlatanov
2017-12-10  7:04                             ` Eli Zaretskii
2017-12-10 13:29                               ` Ted Zlatanov
2017-12-10 14:12                                 ` Eli Zaretskii
2017-12-11 15:03                                   ` Ted Zlatanov
2017-12-11 15:40                                     ` Eli Zaretskii
2017-12-15  4:18                                       ` Ted Zlatanov
2017-12-16 23:25                                         ` Philipp Stephani
2017-12-16 23:34                                           ` Ted Zlatanov
2017-12-17  3:39                                             ` Eli Zaretskii
2017-12-17 15:17                                               ` Eli Zaretskii
2017-12-19 17:46                                                 ` Ted Zlatanov
2017-12-17 17:52                                               ` Philipp Stephani
2017-12-10  9:31                             ` Michael Albinus
2017-12-18 17:16 ` Kaushal Modi
2017-12-18 19:52   ` Philipp Stephani
2017-12-19 17:47   ` Ted Zlatanov
2017-12-19 22:00     ` Kaushal Modi
2017-12-20  1:08       ` Ted Zlatanov
2017-12-20 11:41         ` Robert Pluim
2017-12-20 16:09           ` Eli Zaretskii
2017-12-21 13:20             ` Kaushal Modi
2017-12-21 13:26               ` Ted Zlatanov
2017-12-20 11:48         ` Kaushal Modi
2017-12-20 12:54         ` Andy Moreton
2017-12-20 13:16           ` Andy Moreton
2017-12-20 16:19           ` Eli Zaretskii
2017-12-20 16:38             ` Andy Moreton
2017-12-21  1:15             ` Ted Zlatanov [this message]
2017-12-21  1:39               ` Ted Zlatanov
2017-12-21  8:30                 ` Robert Pluim
2017-12-21 13:12                   ` Ted Zlatanov
2017-12-21 16:20                 ` Eli Zaretskii
2017-12-21 10:54               ` Andy Moreton
2017-12-21 16: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

  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=87a7ycj2yj.fsf@lifelogs.com \
    --to=tzz@lifelogs.com \
    --cc=25061@debbugs.gnu.org \
    --cc=andrewjmoreton@gmail.com \
    --cc=eliz@gnu.org \
    --cc=larsi@gnus.org \
    --cc=ludo@gnu.org \
    --cc=michael.albinus@gmx.de \
    --cc=npostavs@users.sourceforge.net \
    --cc=p.stephani2@gmail.com \
    --cc=wingo@igalia.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 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).