From: Kyle Moffett <mrmacman_g4@mac.com>
To: davids@webmaster.com
Cc: clemens@endorphin.org, linux-kernel@vger.kernel.org
Subject: Re: GPL version, "at your option"?
Date: Wed, 17 Nov 2004 21:12:04 -0500 [thread overview]
Message-ID: <3D5D0803-3907-11D9-85DC-000393ACC76E@mac.com> (raw)
In-Reply-To: <MDEHLPKNGKAHNMBLJOLKEEOHPNAA.davids@webmaster.com>
On Nov 17, 2004, at 20:04, David Schwartz wrote:
> Your logic is totally flawed. Successor versions can certainly add
> limitations.
Your logic is equally flawed.
> Consider the following hypothetical, GPL version 3 allows you to
> relicense
> the code under the FreeBSD license. Someone relicenses Linux (with
> lots of
> later modification) under the FreeBSD license. Now people who receive
> the
> binaries from this new stream of Linux are not entitled to the source
> code.
s/relicense/distribute/g; You can't relicense code without owning the
original
copyright. You _can_ however, receive a license to distribute.
If I receive a binary from them, I receive the original "dual" license.
This means
that anyone who receives it may license it using GPL version "2" or, at
their
option, any later version. This means that when I get some binaries
from some
random company that used your mythical version 3 to distribute under the
terms of any BSD license, I _also_ receive a license to the same code
under
the terms of GPL v2 (at my option :-D). This means that since my
license from
company X is GPL v2 (at my option), I must receive sources under GPL
v2. In
practice this means that you _can't_ change much of what the GPL says in
future versions, at least as far as I can see, without causing said
future version
to be legally invalid.
> Suppose GPL version 3 has no requirement that you make the source
> available. I can then ship Linux without making any source available
> at all
> by claiming that I'm using that later version at my option.
And I can equally legally demand the sources under GPL version 2, at my
option, and you will be forced to give them to me, not at your option
:-D.
Cheers,
Kyle Moffett
-----BEGIN GEEK CODE BLOCK-----
Version: 3.12
GCM/CS/IT/U d- s++: a17 C++++>$ UB/L/X/*++++(+)>$ P+++(++++)>$
L++++(+++) E W++(+) N+++(++) o? K? w--- O? M++ V? PS+() PE+(-) Y+
PGP+++ t+(+++) 5 X R? tv-(--) b++++(++) DI+ D+ G e->++++$ h!*()>++$ r
!y?(-)
------END GEEK CODE BLOCK------
next prev parent reply other threads:[~2004-11-18 2:15 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-16 14:08 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
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 [this message]
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=3D5D0803-3907-11D9-85DC-000393ACC76E@mac.com \
--to=mrmacman_g4@mac.com \
--cc=clemens@endorphin.org \
--cc=davids@webmaster.com \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®