From: Glenn Morris <rgm@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: tchajed@mit.edu, 25967@debbugs.gnu.org, eggert@cs.ucla.edu
Subject: bug#25967: 25.1; Support for ImageMagick 7
Date: Sat, 02 Sep 2017 21:10:49 -0400 [thread overview]
Message-ID: <ucval0twme.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <6a48dc20-17fc-4e4b-b793-4c37c6bcbcc5@Spark>
Eli Zaretskii wrote:
> I agree that would be nicer, but I don't think this minor issue, nor
> the more general one of supporting ImageMagick 7, should block the
> release of Emacs 26.1.
My motivation was that at some point ImageMagick 7 will become the
default version in GNU/Linux distributions. For example, possibly as
soon as Fedora 28, next May, ref
https://pagure.io/fesco/issue/1766
In terms of Emacs releases, this kind of change isn't far away, and
quite possibly before Emacs 27. At some point Emacs will need to support it.
Reference porting info: https://www.imagemagick.org/script/porting.php
next prev parent reply other threads:[~2017-09-03 1:10 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-04 16:17 bug#25967: 25.1; Support for ImageMagick 7 Tej Chajed
2017-03-10 19:03 ` Paul Eggert
2017-07-24 16:41 ` Glenn Morris
2017-07-24 22:15 ` Paul Eggert
2017-07-25 1:25 ` Glenn Morris
2017-09-02 13:06 ` Eli Zaretskii
2017-09-03 1:10 ` Glenn Morris [this message]
2017-12-12 16:59 ` Glenn Morris
2017-12-12 17:15 ` Marcin Borkowski
2017-12-12 17:44 ` Glenn Morris
2018-06-01 19:17 ` bug#25967: [PATCH] Add support for ImageMagick 7 (Bug#25967) Karl Otness
2018-06-23 10:09 ` Kévin Le Gouguec
2018-06-25 21:08 ` Karl Otness
2018-08-28 2:10 ` Glenn Morris
2018-08-28 20:32 ` Karl Otness
2018-08-30 18:00 ` Glenn Morris
2018-08-30 21:53 ` Karl Otness
2018-08-29 3:21 ` Karl Otness
2018-09-03 22:57 ` Andy Moreton
2018-09-04 17:11 ` Eli Zaretskii
2018-09-04 19:03 ` Andy Moreton
2018-09-05 2:38 ` Eli Zaretskii
2018-08-28 2:12 ` bug#25967: 25.1; Support for ImageMagick 7 Glenn Morris
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=ucval0twme.fsf@fencepost.gnu.org \
--to=rgm@gnu.org \
--cc=25967@debbugs.gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=eliz@gnu.org \
--cc=tchajed@mit.edu \
/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).