From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2,2/2] libgdiplus: bump to version 5.6
Date: Sun, 16 Dec 2018 21:17:02 +0100 [thread overview]
Message-ID: <20181216211702.64a7e47f@windsurf.home> (raw)
In-Reply-To: <20180502183336.13568-2-fontaine.fabrice@gmail.com>
Hello,
On Wed, 2 May 2018 20:33:36 +0200, Fabrice Fontaine wrote:
> Add hash for license file
>
> Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
> ---
> Changes v1 -> v2 (after review of Thomas Petazzoni and Sergio Prado):
> - Fix license from MIT to LGPL-2.1 or MPL-1.1 (in a separate patch)
I applied to master. I backported two upstream patches that fix the
license file, so that it is consistent with the comments in the source
code that says the license is MIT. So everything is clear in terms of
licensing now.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2018-12-16 20:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-02 18:33 [Buildroot] [PATCH v2,1/2] libgdiplus: fix license Fabrice Fontaine
2018-05-02 18:33 ` [Buildroot] [PATCH v2,2/2] libgdiplus: bump to version 5.6 Fabrice Fontaine
2018-12-16 20:17 ` 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=20181216211702.64a7e47f@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