From: Greg KH <gregkh@linuxfoundation.org>
To: J Lovejoy <opensource@jilayne.com>
Cc: linux-spdx@vger.kernel.org
Subject: Re: some ideas on guidelines
Date: Sun, 18 Aug 2019 07:08:39 +0200 [thread overview]
Message-ID: <20190818050839.GA5519@kroah.com> (raw)
In-Reply-To: <E76E6780-6CB6-427D-82EB-A84C95656254@jilayne.com>
On Sat, Aug 17, 2019 at 01:55:23PM -0600, J Lovejoy wrote:
> > #4 Where the file contains a license notice that clearly states
> > the file is licensed under “GPL” with no indication of version
> > number and no other license information whatsoever —> ADD SPDX
> > identifier for GPL-2.0-or-later Rationale: This is consistent with
> > the text of the license which states, “If the Program does not
> > specify a version number of this License, you may choose any version
> > ever published by the Free Software Foundation.” Because the Linux
> > kernel is well-known to be licensed under GPL-2.0-only and use of
> > GPL-1.0 is generally sparse, it within the options given in the
> > license text to choose GPL-2.0-or-later in this case. Doing so more
> > easily enables use of such files beyond the Linux kernel.
>
> Please confirm that everyone agrees with this approach, in particular
> that we would leave the existing license notice in place and simply
> ADD the SPDX Identifier.
Sorry, I missed this one. No, I do not agree with this as the kernel
has never been "2 or later" for the main license. "2-only" should be
what is done here as that reflects the license of the kernel as a whole.
Also, I think we caught most of these files already that had this type
of marking, so I don't know if it's even an issue anymore, is it?
And no one except HURD is going to be trying to use Linux files in other
projects :)
thanks,
greg k-h
next prev parent reply other threads:[~2019-08-18 5:08 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-12 5:25 some ideas on guidelines J Lovejoy
2019-06-12 10:26 ` Philippe Ombredanne
2019-06-24 0:57 ` J Lovejoy
2019-06-12 16:04 ` John Sullivan
2019-06-24 1:01 ` J Lovejoy
2019-06-13 17:44 ` Richard Fontana
2019-06-14 14:25 ` Richard Fontana
2019-06-17 4:44 ` J Lovejoy
2019-06-24 1:08 ` J Lovejoy
2019-08-17 19:55 ` J Lovejoy
2019-08-18 5:08 ` Greg KH [this message]
2019-08-18 22:08 ` Richard Fontana
2019-08-19 4:30 ` Christoph Hellwig
2019-08-19 5:06 ` Greg KH
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=20190818050839.GA5519@kroah.com \
--to=gregkh@linuxfoundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.