From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3 0/7] qt5 bump to 5.8.0-rc
Date: Tue, 13 Dec 2016 17:44:24 +0100 [thread overview]
Message-ID: <20161213174424.0d31bd86@free-electrons.com> (raw)
In-Reply-To: <eb25c05c-1027-7c58-92ab-dc513e412907@andin.de>
Hello,
On Tue, 13 Dec 2016 17:24:44 +0100, Andreas Naumann wrote:
> > Do you know when the final 5.8 is supposed to be released? If it's
> > released before Buildroot 2017.02, then we could take your patches
> > right now, and update them to the final release when it comes out. This
> > way, they would get some exposure (both in terms of Buildroot users
> > exposure, and in terms of autobuilder testing).
>
> According to https://wiki.qt.io/Qt_5.8_Release the final release is
> expected January 5th. So it should easily make it into our 2017.02
> release. Of course the early exposure would be highly beneficial.
OK, so we definitely want to merge your patches soon.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-12-13 16:44 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-13 14:59 [Buildroot] [PATCH v3 0/7] qt5 bump to 5.8.0-rc Andreas Naumann
2016-12-13 14:59 ` [Buildroot] [PATCH v3 1/7] qt5: Remove all hashes Andreas Naumann
2016-12-13 15:50 ` Thomas Petazzoni
2016-12-13 16:35 ` Andreas Naumann
2016-12-13 14:59 ` [Buildroot] [PATCH v3 2/7] qt5: bump to 5.8.0-rc Andreas Naumann
2016-12-13 15:53 ` Thomas Petazzoni
2016-12-16 20:30 ` Peter Seiderer
2016-12-19 9:50 ` Andreas Naumann
2016-12-19 20:31 ` Peter Seiderer
2016-12-16 22:03 ` Peter Seiderer
2016-12-19 9:28 ` Andreas Naumann
2016-12-13 14:59 ` [Buildroot] [PATCH v3 3/7] qt5enginio : move into legacy compatibility Andreas Naumann
2016-12-13 14:59 ` [Buildroot] [PATCH v3 4/7] qt53d/qt5quickcontrols2/qt5serialbus : move out of tech preview Andreas Naumann
2016-12-13 14:59 ` [Buildroot] [PATCH v3 5/7] Revert "qt5base: install bundled fonts to target" Andreas Naumann
2016-12-16 20:47 ` Peter Seiderer
2016-12-19 9:13 ` Andreas Naumann
2016-12-13 14:59 ` [Buildroot] [PATCH v3 6/7] qt5declarative: enable Quick for non-GL platforms Andreas Naumann
2016-12-13 14:59 ` [Buildroot] [PATCH v3 7/7] qt5quickcontrols1/2: enable for software renderer Andreas Naumann
2016-12-13 15:49 ` [Buildroot] [PATCH v3 0/7] qt5 bump to 5.8.0-rc Thomas Petazzoni
2016-12-13 16:15 ` Peter Korsgaard
2016-12-13 16:22 ` Thomas Petazzoni
2016-12-13 16:34 ` Peter Korsgaard
2016-12-13 16:34 ` François Perrad
2016-12-13 16:46 ` Peter Korsgaard
2016-12-13 21:13 ` Thomas Petazzoni
2016-12-14 9:50 ` Will Wagner
2016-12-13 16:54 ` Andreas Naumann
2016-12-17 14:47 ` Thomas Petazzoni
2016-12-13 16:24 ` Andreas Naumann
2016-12-13 16:44 ` Thomas Petazzoni [this message]
2016-12-17 14:46 ` Thomas Petazzoni
2016-12-19 9:13 ` Andreas Naumann
2016-12-19 9:26 ` Thomas Petazzoni
2016-12-21 9:13 ` Andreas Naumann
2016-12-21 9:20 ` Thomas Petazzoni
2017-01-02 8:55 ` Andreas Naumann
2017-01-03 12:35 ` Thomas Petazzoni
2017-01-04 17:02 ` Andreas Naumann
2017-01-15 22:04 ` Thomas Petazzoni
2017-01-24 9:50 ` Zoltan Gyarmati
2017-01-24 13:59 ` Andreas Naumann
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=20161213174424.0d31bd86@free-electrons.com \
--to=thomas.petazzoni@free-electrons.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