From: Dmitry Gutov <dgutov@yandex.ru>
To: Eli Zaretskii <eliz@gnu.org>, Alex Branham <branham@utexas.edu>
Cc: monnier@iro.umontreal.ca, agrambot@gmail.com, emacs-devel@gnu.org
Subject: Re: Increase minimum required GTK versions?
Date: Thu, 11 Apr 2019 17:26:31 +0300 [thread overview]
Message-ID: <dc3eb83a-2580-e579-3b9a-f43974aed8af@yandex.ru> (raw)
In-Reply-To: <83wok04obd.fsf@gnu.org>
On 11.04.2019 17:19, Eli Zaretskii wrote:
> So do we care for the few distros which are listed there with
> GTK3 below 3.10? Some versions of Ubuntu and Trisquel are among them.
I'm fairly sure we don't. Like mentioned, Ubuntu 14.04 (which is the
oldest still-maintained LTS release now) has GTK3 3.10.8.
Trisquel I'm less familiar with, but 8.0 is an LTS, and it was released
a year ago. And Trisquel 6.0 was based on Ubuntu 12.04, so that's a good
reason to not support it anyway.
next prev parent reply other threads:[~2019-04-11 14:26 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
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=dc3eb83a-2580-e579-3b9a-f43974aed8af@yandex.ru \
--to=dgutov@yandex.ru \
--cc=agrambot@gmail.com \
--cc=branham@utexas.edu \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.