From: Eli Zaretskii <eliz@gnu.org>
To: Alex <agrambot@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: Increase minimum required GTK versions?
Date: Sun, 07 Apr 2019 22:08:44 +0300 [thread overview]
Message-ID: <83h8b98wg3.fsf@gnu.org> (raw)
In-Reply-To: <87h8b9tz84.fsf@gmail.com> (message from Alex on Sun, 07 Apr 2019 13:03:07 -0600)
> From: Alex <agrambot@gmail.com>
> Date: Sun, 07 Apr 2019 13:03:07 -0600
>
> I'd like to clean up the GTK code a bit by removing some of the obsolete
> codepaths; what's the policy was on supporting obsolete toolkit
> versions?
>
> Looking at the GTK version history [1], the current minimum versions
> were released 2006-07-03 and 2011-02-10. Bumping the versions to 2.14
> (2008-09-04) and 3.10 (2013-09-23) would remove a good few checks. Is
> this still too recent? If not, perhaps the GTK+2 requirement could be
> bumped to the latest (2.24 -- 2011-01-30)?
The main factor is not how many years have passed, it's what the
distros provide.
next prev parent reply other threads:[~2019-04-07 19:08 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 [this message]
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
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=83h8b98wg3.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=agrambot@gmail.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).