linux-spdx.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Allison Randal <allison@lohutok.net>
Cc: Thomas Gleixner <tglx@linutronix.de>, linux-spdx@vger.kernel.org
Subject: Re: clarification on -only and -or-later
Date: Wed, 22 May 2019 17:45:11 +0200	[thread overview]
Message-ID: <20190522154511.GA17763@kroah.com> (raw)
In-Reply-To: <4c1d1302-afe3-febc-ba92-0ff6efdc57d0@lohutok.net>

On Wed, May 22, 2019 at 10:30:07AM -0400, Allison Randal wrote:
> 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.

If we get permission, that's great!  But given that we already have 53
files with that tag today, the odds of someone contacting all of those
owners is going to be hard :(

> 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 would be amazed if anyone ever does a "follow-on" pass of the tree
after we finish with these, other than to add tags to files that sneak
in without them :)

thanks,

greg k-h

  reply	other threads:[~2019-05-22 15:45 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
2019-05-22 15:45               ` Greg KH [this message]
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=20190522154511.GA17763@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=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).