From: Michael Heimpold <mhei@heimpold.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] u-boot license: SPDX GPL-2.0+ deprecated?
Date: Sat, 15 Aug 2015 21:09:22 +0200 [thread overview]
Message-ID: <4265774.5KZ1OqF9IQ@kerker> (raw)
In-Reply-To: <BY1PR0301MB13030A1BC9128289DA7EEC98827C0@BY1PR0301MB1303.namprd03.prod.outlook.com>
Hi Bhupesh,
Am Freitag, 14. August 2015, 08:24:27 schrieb Sharma Bhupesh:
> Hi Wolfgang, Others
>
> I was going through the Software Package Data Exchange (SPDX) licensing terms for GNU General Public License v2.0 or later, as u-boot licensing uses the same on the header files (SPDX-License-Identifier: GPL-2.0+) (please see [1]).
>
> However, on the SPDX license page for GPL-2.0+ it is mentioned that this license has been deprecated since Release 2.0 of the SPDX Specification [2.0rc2] (please see [2]).
>
If I understand this correctly, it's only a interpretation thing.
Before, the short tag "GPL-2.0+" pointed directly to a license "GNU General Public License v2.0 or later"
and "GPL-2.0" pointed directly to "GNU General Public License v2.0 only".
Now with the new "License Expression Syntax", the term "GPL-2.0+" must be
first interpreted, and the result is something like "(GNU General Public License v2.0 only) or later",
which is actual the same as before (at least for me as non-lawyer :-)
> This confuses me. Do we need to change the licensing information text on the header files?
I don't think so. I guess the reason behind is to make it easier for e.g. automatic license
checking.
>
> [1] http://www.denx.de/wiki/U-Boot/Licensing
> [2] http://spdx.org/licenses/GPL-2.0+
>
> Regards,
> Bhupesh
>
Best regards,
Michael
prev parent reply other threads:[~2015-08-15 19:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-14 8:24 [U-Boot] u-boot license: SPDX GPL-2.0+ deprecated? Sharma Bhupesh
2015-08-15 19:09 ` Michael Heimpold [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=4265774.5KZ1OqF9IQ@kerker \
--to=mhei@heimpold.de \
--cc=u-boot@lists.denx.de \
/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