From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] freetype: legal-info: include docs/LICENSE.TXT
Date: Fri, 7 Apr 2017 20:06:20 +0200 [thread overview]
Message-ID: <20170407200620.67780025@free-electrons.com> (raw)
In-Reply-To: <20170407142859.5801-1-peter@korsgaard.com>
Hello,
On Fri, 7 Apr 2017 16:28:58 +0200, Peter Korsgaard wrote:
> LICENSE.TXT gives an overview and explains in detail that freetype is dual
> licensed under the FTL and GPLv2+, so also include it in the license files.
>
> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
> ---
> package/freetype/freetype.mk | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Both applied. Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-04-07 18:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-07 14:28 [Buildroot] [PATCH 1/2] freetype: legal-info: include docs/LICENSE.TXT Peter Korsgaard
2017-04-07 14:28 ` [Buildroot] [PATCH 2/2] icu: legal-info: refer to the real license file Peter Korsgaard
2017-04-07 18:06 ` Thomas Petazzoni [this message]
2017-04-24 19:16 ` [Buildroot] [PATCH 1/2] freetype: legal-info: include docs/LICENSE.TXT Peter Korsgaard
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=20170407200620.67780025@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