Linux-SPDX Archive on
 help / color / Atom feed
From: Greg KH <>
To: Richard Fontana <>
Cc: J Lovejoy <>,
Subject: Re: some ideas on guidelines
Date: Mon, 19 Aug 2019 07:06:02 +0200
Message-ID: <> (raw)
In-Reply-To: <>

On Sun, Aug 18, 2019 at 06:08:40PM -0400, Richard Fontana wrote:
> On Sun, Aug 18, 2019 at 1:08 AM Greg KH <> wrote:
> >
> > And no one except HURD is going to be trying to use Linux files in other
> > projects :)
> I've actually encountered a few cases over the years where there was
> some desire to reuse Linux files, or portions of Linux files anyway,
> in non-Linux projects (and not HURD :), in situations where the
> presumption that the code was copyrightable and that the applicable
> license was GPLv2, or at least GPLv2-only, was problematic. In one of
> these cases, it was a GPLv3 project (Samba) that wished to use the
> Linux code. They ended up asking Red Hat for a GPLv3-or-later license.
> I think both of the non-Samba cases involved some code that was
> generally useful in contexts having nothing to do with the kernel.

Great, but then it should be GPLv2 like the original COPYING file says,
and not "or later" like it never said.

That's my point, yes, other projects use kernel files all the time
(Spongebob squarepants video game stole our string handling functions)
but if they want a different license for it, they need to get permission
to change it.


greg k-h

      parent reply index

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-12  5:25 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
2019-08-18 22:08     ` Richard Fontana
2019-08-19  4:30       ` Christoph Hellwig
2019-08-19  5:06       ` Greg KH [this message]

Reply instructions:

You may reply publically 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Linux-SPDX Archive on

Archives are clonable:
	git clone --mirror linux-spdx/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-spdx linux-spdx/ \
	public-inbox-index linux-spdx

Example config snippet for mirrors

Newsgroup available over NNTP:

AGPL code for this site: git clone public-inbox