From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3 1/1] lua: remove 5.2.x version
Date: Mon, 3 Dec 2018 22:28:08 +0100 [thread overview]
Message-ID: <20181203222808.6dbfdecd@windsurf.home> (raw)
In-Reply-To: <20181202102506.24699-1-francois.perrad@gadz.org>
Hello Fran?ois,
On Sun, 2 Dec 2018 11:25:06 +0100, Francois Perrad wrote:
> At this time :
> - Lua 5.3.5 will be the last one of its serie.
> - Lua 5.4 is up coming (lua-5.4.0-work2 is already available).
> - Lua 5.2.4 was released on 2015.
> For various reasons in the Lua ecosystem, the Lua 5.1 will stay.
> On BR, Lua 5.3 is the default version since 2016.02.
>
> So, the serie which could be removed is the 5.2.x.
> We could wait some days for other user feedback.
>
> Note: see discussion when 5.3.x was introduced : http://lists.busybox.net/pipermail/buildroot/2015-January/117638.html
One quick question: Prosody 0.11 has been released, and they say:
"""
Prosody has traditionally used Lua 5.1. As we announced back when 0.10
was released, we are on the path to updating to more recent Lua
versions.
The recommended Lua version for 0.11 is Lua 5.2, while Lua 5.1 is still
supported for the platforms that need it.
"""
Should we keep Lua 5.2 for Prosody ?
> v2 --> v3
> - rebase on top of BR 2018.11
The changelog should go...
>
> Signed-off-by: Francois Perrad <francois.perrad@gadz.org>
> ---
... here. Otherwise, it becomes part of the commit log when applying,
which we don't want.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-12-03 21:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-02 10:25 [Buildroot] [PATCH v3 1/1] lua: remove 5.2.x version Francois Perrad
2018-12-03 21:28 ` Thomas Petazzoni [this message]
2018-12-04 4:26 ` François Perrad
2018-12-09 20:24 ` Thomas Petazzoni
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=20181203222808.6dbfdecd@windsurf.home \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@busybox.net \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox