From: Stephen Warren <swarren@wwwdotorg.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] SPDX: document dual license notation
Date: Wed, 09 Oct 2013 09:59:29 -0600 [thread overview]
Message-ID: <52557D61.7030801@wwwdotorg.org> (raw)
In-Reply-To: <20131009042358.D2ADD380432@gemini.denx.de>
On 10/08/2013 10:23 PM, Wolfgang Denk wrote:
> Dear Stephen,
>
> In message <52546F78.40300@wwwdotorg.org> you wrote:
>>
>>> +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.
>
> Could you please suggest such a phrase? Thanks.
Sigh. As I said: 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.
next prev parent reply other threads:[~2013-10-09 15:59 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
2013-10-09 4:23 ` Wolfgang Denk
2013-10-09 15:59 ` Stephen Warren [this message]
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=52557D61.7030801@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.