All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: "Luis R. Rodriguez" <mcgrof@frijolero.org>
Cc: "Ted Ts'o" <tytso@mit.edu>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	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>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: [PATCH] module: Clarify GPL-Compatible is OK
Date: Sun, 8 Apr 2012 18:12:27 +0100	[thread overview]
Message-ID: <20120408181227.5d9430d9@pyramind.ukuu.org.uk> (raw)
In-Reply-To: <CAB=NE6X1NFLn6UfPHyNP9_uFTCdYUbtoTP0ds+0YT3_oFCZTSQ@mail.gmail.com>

> > Dual licensing avoids some confusions, it also removes the worry about
> > possible unanticipated incompatibility. Right now if a court somewhere
> > says "Hey you know what - BSD and GPL are not compatible because XYZ" the
> > fact it is dual licensed avoids problems.
> 
> Interesting, I had not considered that case, is this really likely to
> happen now, I mean at least with the list of licenses listed as
> GPL-Compatible on the FSF site?

I would be very surprised - but why chance it ?

> in perspective to what extent do we want to remain speculative over
> the list the FSF provides on GPL-Compatibility for the Linux kernel?
> Are there, say, at least a few GPL-Compatible licenses which we are
> comfortable with in assuming GPL-Compatibility moving forward?

IMHO it's up to whoever wants another tag badly enough to submit a change
for it. Consider it optimising the problem by delayed evaluation.

Alan

  reply	other threads:[~2012-04-08 17:10 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
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 [this message]
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=20120408181227.5d9430d9@pyramind.ukuu.org.uk \
    --to=alan@lxorguk.ukuu.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 \
    --cc=tytso@mit.edu \
    /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.