From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Michael Poole <mdpoole@troilus.org>
Cc: Charles Cazabon <linux@discworld.dyndns.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: GPL version, "at your option"?
Date: Wed, 17 Nov 2004 16:09:33 +0000 [thread overview]
Message-ID: <1100707771.419.58.camel@localhost.localdomain> (raw)
In-Reply-To: <87y8h08mgv.fsf@sanosuke.troilus.org>
On Mer, 2004-11-17 at 16:33, Michael Poole wrote:
> I have no argument that restricting it to v2 is potentially harmful,
> but allowing distribution under GPL v3 is also potentially harmful
> since the terms are not yet known, and later v3plus changes would
> restrict the whole work to v3plus.
Oh believe me I understand exactly why Linus said "v2 only". The GPL say
"similiar license" but Linus doesn't trust Richard. That's fine, I don't
trust Richard or Linus 8)
If people are going to say "v2 only" they should most definitely make
sure they assign Linus or some similar person the right to revisit that
decision.
Alan
next prev parent reply other threads:[~2004-11-17 17:13 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-16 14:08 GPL version, "at your option"? Fruhwirth Clemens
2004-11-16 14:35 ` Erik Mouw
2004-11-16 14:58 ` Fruhwirth Clemens
2004-11-16 14:40 ` Charles Cazabon
2004-11-17 15:07 ` Alan Cox
2004-11-17 16:33 ` Michael Poole
2004-11-17 16:09 ` Alan Cox [this message]
2004-11-16 14:48 ` Tim Schmielau
2004-11-16 15:46 ` Linus Torvalds
2004-11-17 15:09 ` Alan Cox
2004-11-17 16:28 ` Linus Torvalds
2004-11-17 16:16 ` Alan Cox
2004-11-17 17:59 ` Linus Torvalds
2004-11-17 21:11 ` Jesper Juhl
2004-11-16 15:38 ` James Morris
2004-11-18 1:04 ` David Schwartz
2004-11-18 2:12 ` Kyle Moffett
2004-11-18 2:50 ` Dmitry Torokhov
2004-11-18 3:11 ` Kyle Moffett
2004-11-18 4:54 ` Dmitry Torokhov
2004-11-18 15:46 ` David Schwartz
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=1100707771.419.58.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@discworld.dyndns.org \
--cc=mdpoole@troilus.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