From: Glenn Morris <rgm@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: dr.khaled.hosny@gmail.com, behdad@behdad.org,
33748@debbugs.gnu.org, far.nasiri.m@gmail.com
Subject: bug#33748: 27.0.50; harfbuzz branch fails to compile
Date: Mon, 17 Dec 2018 14:13:46 -0500 [thread overview]
Message-ID: <yjmup4j79x.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <835zvufvwf.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 15 Dec 2018 21:10:56 +0200")
Eli Zaretskii wrote:
> The last part, in my interpretation, means 0.9.42 is "good enough",
> since it has the APIs used by the code.
I feel like I'm flogging a dead horse, but to me there's a difference
between "good enough" and "the minimum version that we want to support
going forward". Is anyone going to be testing 0.9.42 on a regular basis?
It looks 0.9.42 and 1.0 were released on the same day, so requiring the
former instead of the latter makes little sense to me.
Debian stable has 1.4.2, RHEL 7 has 1.7.5, Ubuntu 16.04 has 1.0.1,
Ubuntu 18.04 has 1.7.2.
So personally I would set the minimum to 1.4.2 (Jan 2017).
And that's all I have to say about that. :)
prev parent reply other threads:[~2018-12-17 19:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-14 20:27 bug#33748: 27.0.50; harfbuzz branch fails to compile Eli Zaretskii
2018-12-14 20:44 ` Glenn Morris
2018-12-15 6:44 ` Eli Zaretskii
2018-12-15 7:34 ` Colin Baxter
2018-12-15 11:24 ` Colin Baxter
2018-12-15 12:05 ` Eli Zaretskii
2018-12-14 22:52 ` Khaled Hosny
2018-12-15 6:59 ` Eli Zaretskii
2018-12-15 7:13 ` Eli Zaretskii
2018-12-15 10:32 ` Khaled Hosny
2018-12-15 10:37 ` Eli Zaretskii
2018-12-15 10:32 ` Khaled Hosny
2018-12-15 17:50 ` Glenn Morris
2018-12-15 19:10 ` Eli Zaretskii
2018-12-17 19:13 ` Glenn Morris [this message]
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=yjmup4j79x.fsf@fencepost.gnu.org \
--to=rgm@gnu.org \
--cc=33748@debbugs.gnu.org \
--cc=behdad@behdad.org \
--cc=dr.khaled.hosny@gmail.com \
--cc=eliz@gnu.org \
--cc=far.nasiri.m@gmail.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).