From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] qt5webengine: update chromium license file names
Date: Wed, 29 Aug 2018 10:24:13 +0200 [thread overview]
Message-ID: <20180829102413.5c93b057@windsurf> (raw)
In-Reply-To: <20180829063034.10766-1-laurent.hartanerot@gmail.com>
Hello Laurent,
On Wed, 29 Aug 2018 08:30:34 +0200, Laurent Hartanerot wrote:
> From: Laurent Hartanerot <laurent.hartanerot@atos.net>
>
> For the 2018.05.x branch:
> Update license file name for qt5webengine-5.6.3
> (Last version on the 2018.05.x branch)
>
> Signed-off-by: Laurent Hartanerot <laurent.hartanerot@atos.net>
Same comments here: why only for the 2018.05.x branch, and not for
master ? Do this work for both Qt 5.6 and Qt 5.11 ?
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-08-29 8:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-29 6:30 [Buildroot] [PATCH 1/1] qt5webengine: update chromium license file names Laurent Hartanerot
2018-08-29 8:24 ` Thomas Petazzoni [this message]
2018-08-29 10:45 ` Laurent Hartanerot
2018-08-29 10:51 ` [Buildroot] [PATCH v2 " Laurent Hartanerot
2018-08-29 20:32 ` Thomas Petazzoni
2018-08-30 6:13 ` Laurent Hartanerot
2018-09-01 8:02 ` Gaël PORTAY
2018-08-30 10:05 ` [Buildroot] [PATCH v3 1/3] qt5webengine: update chromium license file names for qt-lts Laurent Hartanerot
2018-09-01 12:46 ` Thomas Petazzoni
2018-09-27 21:12 ` Peter Korsgaard
2018-08-30 10:06 ` [Buildroot] [PATCH v3 2/3] qt5webengine: update chromium license file names for qt-latest Laurent Hartanerot
2018-09-01 12:46 ` Thomas Petazzoni
2018-08-30 10:07 ` [Buildroot] [PATCH v3 3/3] qt5webengine: Rename internal variable to qt5webengine Laurent Hartanerot
2018-09-01 12:47 ` 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=20180829102413.5c93b057@windsurf \
--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