From: Greg KH <gregkh@linuxfoundation.org>
To: Richard Fontana <rfontana@redhat.com>
Cc: J Lovejoy <opensource@jilayne.com>, linux-spdx@vger.kernel.org
Subject: Re: some ideas on guidelines
Date: Mon, 19 Aug 2019 07:06:02 +0200 [thread overview]
Message-ID: <20190819050602.GA10236@kroah.com> (raw)
In-Reply-To: <CAC1cPGwDOeeFN5EmZjhT_Ge+95i=thgKAP_kjJiEKc_KciMftw@mail.gmail.com>
On Sun, Aug 18, 2019 at 06:08:40PM -0400, Richard Fontana wrote:
> On Sun, Aug 18, 2019 at 1:08 AM Greg KH <gregkh@linuxfoundation.org> 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.
thanks,
greg k-h
prev parent reply other threads:[~2019-08-19 5:06 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
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 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=20190819050602.GA10236@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=linux-spdx@vger.kernel.org \
--cc=opensource@jilayne.com \
--cc=rfontana@redhat.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.