public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Fruhwirth Clemens <clemens@endorphin.org>
To: linux-kernel@vger.kernel.org, James Morris <jmorris@redhat.com>,
	Linus Torvalds <torvalds@osdl.org>
Subject: GPL version, "at your option"?
Date: Tue, 16 Nov 2004 15:08:35 +0100	[thread overview]
Message-ID: <1100614115.16127.16.camel@ghanima> (raw)

[-- Attachment #1: Type: text/plain, Size: 1488 bytes --]

Standard template for GPL licensing:

"This program is free software; you can redistribute it and/or modify it
under the terms of the GNU General Public License as published by the
Free Software Foundation; either version 2 of the License, or (at your
option) any later version."

As the text says, the licensee can choose the GPL version at his option,
and he is likely to choose the one with better conditions. So, newer
version can never limit the licensee's right, because he is always free
to choose version 2. Therefore, successor versions can only remove
limitations. 

The institution to decide, how the new versions look like, is FSF. Being
totally paranoid, assume the FSF decision makers are infected by a SCO
designed virus to make them publish a new GPL version giving SCO the
right to exploit GPL covered intellectual property. And there is a lot
of the latter. Would be a classical "Duh!" situation.

I'm about to submit a patch for a new cipher mode called LRW, adding new
code/files to the crypto tree. My question is, especially to the
maintainers: Are you going to accept code covered by the terms:

 * This program is free software; you can redistribute it and/or modify
 * it under the terms of the GNU General Public License as published by
 * the Free Software Foundation, version 2 of the License.
                                 ^^^^^^^^^^^^^^^^^^^^^^^^^

-- 
Fruhwirth Clemens <clemens@endorphin.org>  http://clemens.endorphin.org

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

             reply	other threads:[~2004-11-16 14:24 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-16 14:08 Fruhwirth Clemens [this message]
2004-11-16 14:35 ` GPL version, "at your option"? 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
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=1100614115.16127.16.camel@ghanima \
    --to=clemens@endorphin.org \
    --cc=jmorris@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@osdl.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