From: Dmitry Torokhov <dtor_core@ameritech.net>
To: Kyle Moffett <mrmacman_g4@mac.com>
Cc: clemens@endorphin.org, davids@webmaster.com,
linux-kernel@vger.kernel.org
Subject: Re: GPL version, "at your option"?
Date: Wed, 17 Nov 2004 23:54:19 -0500 [thread overview]
Message-ID: <200411172354.19223.dtor_core@ameritech.net> (raw)
In-Reply-To: <81348C10-390F-11D9-85DC-000393ACC76E@mac.com>
On Wednesday 17 November 2004 10:11 pm, Kyle Moffett wrote:
> 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.
> 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
No, not at all. I need only _one_ license to use the code. If original
code was dual-licensed, let's say GPL/BSD, I can chose to completely
ignore GPL part and treat the code as if it was always released BSD only.
Why do you think several components, like ACPI, are dual-licensed?
Intel chose to do that so they can take ACPI interpreter implementation
and use it somewhere else, in non-GPL environment.
Q9. Under what licensing is the source released?
A9. ACPI CA can be licensed under the GNU General Public License or via a
separate license that may be more favorable to commercial OSVs. Please
see the source code license header for specifics.
> (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.
See above. For me it was never GPLv2, if was BSD all the way and my new
code I can chose to make BSD only.
--
Dmitry
next prev parent reply other threads:[~2004-11-18 4:55 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
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 [this message]
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=200411172354.19223.dtor_core@ameritech.net \
--to=dtor_core@ameritech.net \
--cc=clemens@endorphin.org \
--cc=davids@webmaster.com \
--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