From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3 0/5] Update Qt5 to 5.12.1
Date: Sat, 23 Feb 2019 17:03:23 +0100 [thread overview]
Message-ID: <20190223170323.14b17270@windsurf.home> (raw)
In-Reply-To: <20190217141209.22182-1-thomas.petazzoni@bootlin.com>
Hello,
On Sun, 17 Feb 2019 15:12:04 +0100
Thomas Petazzoni <thomas.petazzoni@bootlin.com> wrote:
> Peter Seiderer (1):
> package/qt5: bump latest version to 5.12.1
>
> Thomas Petazzoni (4):
> package/qt5/qt5webengine: sort chromium-{latest,lts}.inc files
> package/qt5/qt5webengine: generate chromium-latest.inc automatically
> package/qt5/qt5webengine: generate chromium-lts.inc automatically
> package/qt5/qt5webengine: add hashes for license files
I've applied the series to next. Thanks a lot Peter for your review!
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2019-02-23 16:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-17 14:12 [Buildroot] [PATCH v3 0/5] Update Qt5 to 5.12.1 Thomas Petazzoni
2019-02-17 14:12 ` [Buildroot] [PATCH v3 1/5] package/qt5/qt5webengine: sort chromium-{latest, lts}.inc files Thomas Petazzoni
2019-02-23 12:29 ` Peter Seiderer
2019-02-17 14:12 ` [Buildroot] [PATCH v3 2/5] package/qt5/qt5webengine: generate chromium-latest.inc automatically Thomas Petazzoni
2019-02-23 12:30 ` Peter Seiderer
2019-02-17 14:12 ` [Buildroot] [PATCH v3 3/5] package/qt5/qt5webengine: generate chromium-lts.inc automatically Thomas Petazzoni
2019-02-23 12:30 ` Peter Seiderer
2019-02-17 14:12 ` [Buildroot] [PATCH v3 4/5] package/qt5: bump latest version to 5.12.1 Thomas Petazzoni
2019-02-23 12:32 ` Peter Seiderer
2019-02-17 14:12 ` [Buildroot] [PATCH v3 5/5] package/qt5/qt5webengine: add hashes for license files Thomas Petazzoni
2019-02-23 12:32 ` Peter Seiderer
2019-02-23 16:03 ` Thomas Petazzoni [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190223170323.14b17270@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