From: Al Viro <viro@ZenIV.linux.org.uk>
To: "Luis R. Rodriguez" <mcgrof@frijolero.org>
Cc: rusty@rustcorp.com.au, linux-kernel@vger.kernel.org,
Keith Packard <keithp@keithp.com>,
Ralf Baechle <ralf@linux-mips.org>,
David Woodhouse <dwmw2@infradead.org>,
Stephen Hemminger <shemminger@vyatta.com>,
"John W. Linville" <linville@tuxdriver.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: [PATCH] module: Clarify GPL-Compatible is OK
Date: Sat, 7 Apr 2012 01:28:28 +0100 [thread overview]
Message-ID: <20120407002828.GG6589@ZenIV.linux.org.uk> (raw)
In-Reply-To: <1333757482-16204-1-git-send-email-mcgrof@frijolero.org>
On Fri, Apr 06, 2012 at 05:11:22PM -0700, Luis R. Rodriguez wrote:
> You do not need to make dual licenses when licenses are compatible
> with each other, and in fact at times this can confuse developers / legal.
> This has been well documented by SFLC through their "Maintaining
> Permissive-Licensed Files in a GPL-Licensed Project: Guidelines for
> Developers" [0] which was inspired by the ambiguity of the MadWifi
> Project's Dual BSD/GPL license tradition. The list of GPL-Compatible
> licenses can be found on the FSF's website [1].
This is obvious crap. Explain to me, please, what makes your "GPL compatible"
different from "GPLv2"; at least that would be honest ("we have relicensed
a copy of BSD/GPL code to GPL alone - the license allows that and any
modifications done here are declared GPL-only, so you can't pull them into
the BSD-licensed variants")
"GPL compatible" is not a license; it's a set of licenses. Incidentally,
belonging to that set is irrelevant to legality of including into the kernel,
since GPLv3 a member and it's *NOT* compatible with the kernel license.
since GPLv3 a member and it's *NOT* compatible with the kernel license.
next prev parent reply other threads:[~2012-04-07 0:28 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-07 0:11 [PATCH] module: Clarify GPL-Compatible is OK Luis R. Rodriguez
2012-04-07 0:27 ` Greg Kroah-Hartman
2012-04-07 0:28 ` Al Viro [this message]
2012-04-07 0:57 ` Luis R. Rodriguez
2012-04-07 0:36 ` Linus Torvalds
2012-04-07 0:51 ` Luis R. Rodriguez
2012-04-07 1:02 ` Luis R. Rodriguez
2012-04-08 12:42 ` Arend van Spriel
2012-04-07 2:49 ` Ted Ts'o
2012-04-07 3:01 ` Luis R. Rodriguez
2012-04-07 21:15 ` Ted Ts'o
2012-04-08 0:52 ` Luis R. Rodriguez
2012-04-08 14:57 ` Alan Cox
2012-04-08 16:06 ` Luis R. Rodriguez
2012-04-08 17:12 ` Alan Cox
2012-04-08 20:23 ` Ted Ts'o
2012-04-07 19:03 ` Alan Cox
2012-04-08 12:49 ` Arend van Spriel
2012-04-08 22:50 ` Dan Williams
2012-05-07 2:39 ` Rusty Russell
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=20120407002828.GG6589@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=dwmw2@infradead.org \
--cc=gregkh@linuxfoundation.org \
--cc=keithp@keithp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=mcgrof@frijolero.org \
--cc=ralf@linux-mips.org \
--cc=rusty@rustcorp.com.au \
--cc=shemminger@vyatta.com \
--cc=torvalds@linux-foundation.org \
/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