From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [RFC] SPDX License text updates
Date: Mon, 22 Jan 2018 12:06:07 -0500 [thread overview]
Message-ID: <20180122170607.GL32220@bill-the-cat> (raw)
Hey all,
In another thread Felix Brack brought up that as of version 3.0 of SPDX,
there's a number of deprecated tags (see https://spdx.org/licenses/) and
that we're using at least one of them.
Specifically, "GPL-2.0+" should be "GPL-2.0-or-later".
Now, we have a few options here:
- Deprecated isn't removed. SPDX specifically says the old links shall
remain valid, etc, etc. We could continue to use "GPL-2.0+", etc and
not have to change (literally) 8000 files. This will also keep us in
line with what the Linux kernel currently does. I also have no idea,
nor have I looked to see if that's going to change.
- Allow both old and new. Both are valid, the newer form allows for
easier tooling and more precise management of options that I'm not
sure apply to our use cases.
- Switch to the new tags. A few hour I imagine of playing around with
sed and then manual fixups and I can probably convert all the existing
cases to the new syntax (we have some DTS files for example with
(GPL-2.0+ OR MIT) which would become (GPL-2.0-or-later OR MIT). But
then we need some tooling to make checkpatch.pl at least noisy about
unconverted and to get everyone into the habit of changing and so
forth.
At this point in time I'm leaning towards the first, and as is often the
case, watching what the kernel does. Thoughts / comments? Thanks!
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20180122/8db2b457/attachment.sig>
next reply other threads:[~2018-01-22 17:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-22 17:06 Tom Rini [this message]
2018-01-22 19:44 ` [U-Boot] [RFC] SPDX License text updates Wolfgang Denk
2018-01-22 20:11 ` Tom Rini
2018-01-22 21:33 ` Lukasz Majewski
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=20180122170607.GL32220@bill-the-cat \
--to=trini@konsulko.com \
--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