From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] dual licensed files
Date: Fri, 26 Jul 2013 23:45:45 +0200 [thread overview]
Message-ID: <20130726214545.5BC9E3803E7@gemini.denx.de> (raw)
In-Reply-To: <047701ce8a46$bcc78820$36569860$@bufferoverflow.ch>
Dear Roger,
In message <047701ce8a46$bcc78820$36569860$@bufferoverflow.ch> you wrote:
> Thank you Wolfgang for simplifying license handling!
You are welcome!
> What about dual licensed files? What do you prefer?
>
> SPDX-License-Identifier: GPL-2.0+
> SPDX-License-Identifier: BSD-2-Clause
This was my initial idea when I started thinking about this, but then
I realized that there were a few files that had (by accident) both
GPL-2.0+ and GPL-2.0 license headers (separated by a larger text
block, so it was not obvious at first glance), so my first attempts of
automatic editing would generate two (here incompatible) License-ID
entries.
Because of this I think there should be exactly one License-ID entry
in any file. So for dual-licensed files the entry should list the
license IDs in a single entry.
> SPDX-License-Identifier: GPL-2.0+, BSD-2-Clause
> Other seperator?
Yes, please let's just use white space for separation; this is easier
to parse by simple (shell) scripts.
Best regards,
Wolfgang Denk
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
"I've seen it. It's rubbish." - Marvin the Paranoid Android
next prev parent reply other threads:[~2013-07-26 21:45 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 [this message]
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
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=20130726214545.5BC9E3803E7@gemini.denx.de \
--to=wd@denx.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