linux-spdx.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: J Lovejoy <opensource@jilayne.com>
Cc: "Bradley M. Kuhn" <bkuhn@ebb.org>, linux-spdx@vger.kernel.org
Subject: Re: clarification on -only and -or-later
Date: Wed, 22 May 2019 15:23:47 +0200	[thread overview]
Message-ID: <20190522132347.GC28920@kroah.com> (raw)
In-Reply-To: <595412F8-2FA4-4898-8B98-0251D493CBDA@jilayne.com>

On Tue, May 21, 2019 at 12:05:37PM -0600, J Lovejoy wrote:
> > I agree that one can use GPL-1.0-or-later in this case well (which was
> > discussed down thread), but I also agree with the argument (also downthread)
> > that there is no *requirement* to include GPL-1.0 in the mix.  The text of
> > the COPYING file (i.e., GPLv2) is clear on this point, if we have code that
> > does "not specify a version number of this License, you may choose any
> > version ever published by the Free Software Foundation."
> > 
> > Jilayne and I did a pretty deep dive on this question of the 'no version
> > number specified' and I think our discussions made us sure that it does
> > *not* mean GPL-2.0-only, because of the text above.  I checked with
> > Fontana too and he agrees with this as well.
> 
> I think what I was looking for here, was confirmation as to whether we
> want to do the “literal” GPL-1.0-or-later option that the license
> provides for, or trigger the option to “choose any version” and go
> with GPL-2.0-or-later for consistency of v2 across the kernel and for
> other reasons I believe you raised regarding GPL-1.0

I don't understand.  Can you point to any files in the kernel where we
have used the "GPL-1.0+" marking incorrectly?

thanks,

greg k-h

  reply	other threads:[~2019-05-22 13:23 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 [this message]
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
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=20190522132347.GC28920@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=bkuhn@ebb.org \
    --cc=linux-spdx@vger.kernel.org \
    --cc=opensource@jilayne.com \
    /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).