From: Glenn Morris <rgm@gnu.org>
To: Alex <agrambot@gmail.com>
Cc: Eli Zaretskii <eliz@gnu.org>, Paul Eggert <eggert@cs.ucla.edu>,
emacs-devel@gnu.org
Subject: Re: Increase minimum required GTK versions?
Date: Mon, 08 Apr 2019 12:15:11 -0400 [thread overview]
Message-ID: <ee36msh3sg.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <87y34kiloy.fsf@gmail.com> (Alex's message of "Mon, 08 Apr 2019 09:03:09 -0600")
Alex wrote:
> Do we really have to consider RHEL 5, considering that it's on "Extended
> Life Cycle Support"[1]? If someone is paying extra for post-Production
> support for a "retired"[1] enterprise distro from 2007, then I doubt
> that they or their users will be running the latest Emacs, especially a
> GTK build instead of terminal-only or another toolkit such as Lucid.
I'm a long-term RHEL user, and I completely agree that there is no need
for Emacs 27 to worry about supporting RHEL5 (at all, never mind for GTK).
(IIRC, RHEL5 shipped with Emacs 21.)
(Since RHEL7 was released 5 years ago, I also have no problem with
dropping RHEL6 support in Emacs 27 if it makes maintenance significantly
easier.)
next prev parent reply other threads:[~2019-04-08 16:15 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-07 19:03 Increase minimum required GTK versions? Alex
2019-04-07 19:08 ` Eli Zaretskii
2019-04-07 19:25 ` Alex
2019-04-08 4:45 ` Paul Eggert
2019-04-08 15:03 ` Alex
2019-04-08 16:03 ` Kaushal Modi
2019-04-08 16:15 ` Glenn Morris [this message]
2019-04-08 23:58 ` Paul Eggert
2019-04-09 1:55 ` Stefan Monnier
2019-04-09 4:47 ` Paul Eggert
2019-04-09 17:28 ` Alex
2019-04-09 18:21 ` Eli Zaretskii
2019-04-10 3:14 ` Alex
2019-04-10 15:57 ` Eli Zaretskii
2019-04-10 16:20 ` Stefan Monnier
2019-04-10 16:43 ` Eli Zaretskii
2019-04-11 0:35 ` Alex
2019-04-11 1:26 ` Alex Branham
2019-04-11 14:19 ` Eli Zaretskii
2019-04-11 14:26 ` Dmitry Gutov
2019-04-11 14:29 ` Alex
2019-04-12 18:49 ` Eli Zaretskii
2019-04-12 19:05 ` Alex Gramiak
2019-04-12 19:14 ` Eli Zaretskii
2019-04-12 19:33 ` Alex Gramiak
2019-04-12 19:45 ` Eli Zaretskii
2019-04-12 20:04 ` Alex Gramiak
2019-04-12 20:17 ` Eli Zaretskii
2019-04-09 5:00 ` Van L
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=ee36msh3sg.fsf@fencepost.gnu.org \
--to=rgm@gnu.org \
--cc=agrambot@gmail.com \
--cc=eggert@cs.ucla.edu \
--cc=eliz@gnu.org \
--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).