From: Stephen Warren <swarren@wwwdotorg.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] SPDX: document dual license notation
Date: Tue, 08 Oct 2013 14:47:52 -0600 [thread overview]
Message-ID: <52546F78.40300@wwwdotorg.org> (raw)
In-Reply-To: <1381262025-10154-1-git-send-email-wd@denx.de>
On 10/08/2013 01:53 PM, Wolfgang Denk wrote:
> In [1] we discussed how we should deal with dual (or, more generally,
> multiple) licensed files. Add this to Licenses/README so it's
> properly documented.
>
> [1] http://thread.gmane.org/gmane.comp.boot-loaders.u-boot/166518
>
> Signed-off-by: Wolfgang Denk <wd@denx.de>
> ---
> Licenses/README | 12 ++++++++++++
> 1 file changed, 12 insertions(+)
>
> diff --git a/Licenses/README b/Licenses/README
> index 9f61192..6dd7d5b 100644
> --- a/Licenses/README
> +++ b/Licenses/README
> @@ -37,6 +37,18 @@ replaced by a single line:
>
> SPDX-License-Identifier: GPL-2.0+
>
> +Ideally, the license terms of all files in the source tree should be
> +defined by such License Identifiers; in no case a file can contain
> +more than one such License Identifier.
I assume "one such License Identifier" here is intended to mean: a
source line prefixed with the words "SPDX-License-Identifier:". However,
to me "one such License Identifier" would actually refer to the
"GPL-2.0+" part of the line, since that's what actually identifies the
license. The other text simply introduces a list of license identifiers.
That would then conflict with the rest of the patch that goes on to
explicitly state that multiple licenses are allowed.
In other words, I think that text can be confusing. I think you need to
add "line", "list" or "set" to the end of the sentence to make it
unambiguous.
> +If a "SPDX-License-Identifier:" line references more than one Unique
> +License Identifier, then this means that the respective file can be
> +used under the terms of either of these licenses, i. e. with
> +
> + SPDX-License-Identifier: GPL-2.0+ BSD-3-Clause
> +
> +you can chose between GPL-2.0+ and BSD-3-Clause licensing.
next prev parent reply other threads:[~2013-10-08 20:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-26 21:26 [U-Boot] dual licensed files Roger Meier
2013-07-26 21:45 ` Wolfgang Denk
2013-10-08 19:53 ` [U-Boot] [PATCH] SPDX: document dual license notation Wolfgang Denk
2013-10-08 20:47 ` Stephen Warren [this message]
2013-10-09 4:23 ` Wolfgang Denk
2013-10-09 15:59 ` Stephen Warren
2013-10-14 20:27 ` [U-Boot] " Tom Rini
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=52546F78.40300@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--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