From: "David Schwartz" <davids@webmaster.com>
To: <mrmacman_g4@mac.com>, "Dmitry Torokhov" <dtor_core@ameritech.net>
Cc: <clemens@endorphin.org>, <linux-kernel@vger.kernel.org>
Subject: RE: GPL version, "at your option"?
Date: Thu, 18 Nov 2004 07:46:01 -0800 [thread overview]
Message-ID: <MDEHLPKNGKAHNMBLJOLKCECDPOAA.davids@webmaster.com> (raw)
In-Reply-To: <81348C10-390F-11D9-85DC-000393ACC76E@mac.com>
> On Nov 17, 2004, at 21:50, Dmitry Torokhov wrote:
> > Yes, but the additions I made will be GPLv3 only (no sources). So I
> > will
> > gladly provide you with the sources off kernel.org and you will never
> > see
> > the sources for a driver I wrote. See?
>
> What about section 2, subsection B of the GPL:
> > b) You must cause any work that you distribute or publish, that in
> > whole or in part contains or is derived from the Program or any
> > part thereof, to be licensed as a whole at no charge to all third
> > parties under the terms of this License.
>
> "this License", would refer to the specific version of the license.
Precisely!
> This means
> that since the original code is dual-licensed under both versions, any
> code
> that is a derivative work must _also_ be dual-licensed (This assumes of
> course that the other license has a similar clause). In any case, any
> work
> derived from a GPLv2'ed work must also be licensable under the GPLv2.
> Therefore, my request for _your_ source-code under the GPLv2 is
> perfectly
> valid.
No, the code being dual-licensed means you get to choose which license you
wish to comply with, not that you must comply with both. So long as you
comply with either license, you have the right to do whatever the license
you comply with gives you the right to do.
Let's suppose, hypothetically, that you were right. Then let's further
suppose that GPL version 3 did not let you modify the source code at all.
Would you argue that all code with the "at your option" clause now can't be
modified? (Since modifying it would violate the GPLv3 license, and you seem
to think you can't violate either license.)
DS
prev parent reply other threads:[~2004-11-18 15:50 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
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 [this message]
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=MDEHLPKNGKAHNMBLJOLKCECDPOAA.davids@webmaster.com \
--to=davids@webmaster.com \
--cc=clemens@endorphin.org \
--cc=dtor_core@ameritech.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mrmacman_g4@mac.com \
/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
Powered by JetHome