From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 5/6] package/gnu-efi: fix legal-info
Date: Sun, 5 Apr 2015 19:17:45 +0200 [thread overview]
Message-ID: <20150405191745.3497f9a7@free-electrons.com> (raw)
In-Reply-To: <41ea946a815b2214044827c73815d8a171a3a939.1428252467.git.yann.morin.1998@free.fr>
Dear Yann E. MORIN,
On Sun, 5 Apr 2015 18:48:26 +0200, Yann E. MORIN wrote:
> Fix a bunch of deficiencies:
> - 'debian/copyright' does not exist.
> - gnuefi is not GPLv2+. Only one AArch64 file has GPLv2+ headers,
> all others have BSD-3c
> - efilib is BSD-2c
I don't quite agree here: some ARM files are also under GPLv2+, so I
believe the whole thing really is under GPLv2+.
This is also apparently the opinion of Debian:
http://changelogs.ubuntu.com/changelogs/pool/main/g/gnu-efi/gnu-efi_3.0i-2ubuntu1/copyright.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-04-05 17:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-05 16:48 [Buildroot] [PATCH 0/6] legal-info: fix packages (branch yem/legal) Yann E. MORIN
2015-04-05 16:48 ` [Buildroot] [PATCH 1/6] package/liblinear: fix legal-info Yann E. MORIN
2015-04-05 16:48 ` [Buildroot] [PATCH 2/6] package/python-cherrypy: " Yann E. MORIN
2015-04-05 16:48 ` [Buildroot] [PATCH 3/6] package/zmqpp: " Yann E. MORIN
2015-04-05 16:48 ` [Buildroot] [PATCH 4/6] package/evemu: " Yann E. MORIN
2015-04-05 16:48 ` [Buildroot] [PATCH 5/6] package/gnu-efi: " Yann E. MORIN
2015-04-05 17:17 ` Thomas Petazzoni [this message]
2015-04-05 17:31 ` Yann E. MORIN
2015-04-05 17:36 ` Thomas Petazzoni
2015-04-05 17:40 ` Yann E. MORIN
2015-04-05 16:48 ` [Buildroot] [PATCH 6/6] package/linux-firmware: " Yann E. MORIN
2015-04-05 17:17 ` [Buildroot] [PATCH 0/6] legal-info: fix packages (branch yem/legal) 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=20150405191745.3497f9a7@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