From: Allison Randal <allison@lohutok.net>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: linux-spdx@vger.kernel.org
Subject: Re: clarification on -only and -or-later
Date: Wed, 22 May 2019 10:30:07 -0400 [thread overview]
Message-ID: <4c1d1302-afe3-febc-ba92-0ff6efdc57d0@lohutok.net> (raw)
In-Reply-To: <alpine.DEB.2.21.1905221617230.1637@nanos.tec.linutronix.de>
On 5/22/19 3:20 PM, Thomas Gleixner wrote:
> Yes and no. There is a good reason to remove the GPL1+ crap completely and
> I already got permission from Redhat to change their GPL/GPL'ed notices to
> GPL-2.0-or-later. So once we get to that pile we might at least try to talk
> with the copyright holders and clarify it. Each odd license which gets
> removed is a win.
We don't necessarily have to do everything in one pass. We could keep
this round of cleanup strictly to an exact substitution of
GPL-1.0-or-later, and do a separate pass at some point in the future to
deprecate and remove GPL-1.0 where possible.
I'm not sure whether it would be easier to do it all now or save the
deprecation for later. I guess we can see how many files match the
patterns with no version numbers. (With 5 files it's easy to contact the
copyright holders, hundreds would be difficult.)
Allison
next prev parent reply other threads:[~2019-05-22 14:30 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-20 18:40 clarification on -only and -or-later J Lovejoy
2019-05-20 18:52 ` Greg KH
2019-05-20 19:26 ` J Lovejoy
2019-05-20 21:35 ` Allison Randal
2019-05-20 22:09 ` J Lovejoy
2019-05-20 22:19 ` Allison Randal
2019-05-20 22:52 ` J Lovejoy
2019-05-20 23:15 ` Allison Randal
2019-05-21 17:24 ` Bradley M. Kuhn
2019-05-21 18:05 ` J Lovejoy
2019-05-22 13:23 ` Greg KH
2019-05-22 13:53 ` Allison Randal
2019-05-22 14:00 ` Greg KH
2019-05-22 14:20 ` Thomas Gleixner
2019-05-22 14:30 ` Allison Randal [this message]
2019-05-22 15:45 ` Greg KH
2019-05-22 19:04 ` Bradley M. Kuhn
2019-05-22 14:22 ` Allison Randal
2019-05-22 15:03 ` J Lovejoy
[not found] ` <5EB6B416-F24C-4741-BC0E-6C1896E7A705@jilayne.com>
2019-05-21 21:14 ` Bradley M. Kuhn
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=4c1d1302-afe3-febc-ba92-0ff6efdc57d0@lohutok.net \
--to=allison@lohutok.net \
--cc=linux-spdx@vger.kernel.org \
--cc=tglx@linutronix.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;
as well as URLs for NNTP newsgroup(s).