From: Luke -Jr <luke@dashjr.org>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] QEMU License and proprietary hardware
Date: Fri, 22 Jun 2007 10:18:01 -0500 [thread overview]
Message-ID: <200706221018.01516.luke@dashjr.org> (raw)
In-Reply-To: <20070621.163358.-1947356063.imp@bsdimp.com>
On Thursday 21 June 2007 17:33, M. Warner Losh wrote:
> The GPL only has as much force of law as copyright law gives it, and in
> order to be applicable, the work in question must somehow rely on the GPL'd
> work. The "somehow" here is an interesting legal question that hasn't been
> well settled.
And copyright law by default grants you no rights to modify or copy Qemu at
all. The ONLY way you can get permission to copy or modify Qemu is to agree
to the GPL in its entirety-- which does not restrict itself to merely
derivative works, but covers all linking. (note: obvious the copyright
holder(s) can make exceptions to this rule)
IANAL either, but as much as I have to debate this I might as well be
next prev parent reply other threads:[~2007-06-22 15:18 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-21 11:28 [Qemu-devel] QEMU License and proprietary hardware Armbrost Failsafe
2007-06-21 22:24 ` Luke -Jr
2007-06-21 22:33 ` M. Warner Losh
2007-06-22 15:18 ` Luke -Jr [this message]
2007-06-22 16:07 ` Warner Losh
2007-06-22 16:23 ` Luke -Jr
2007-06-22 16:46 ` M. Warner Losh
2007-06-22 17:11 ` Luke -Jr
2007-06-22 17:30 ` M. Warner Losh
2007-06-22 17:31 ` Ronnie Misra
2007-06-22 17:37 ` Johannes Schindelin
2007-06-22 18:00 ` Luke -Jr
2007-06-22 18:22 ` Johannes Schindelin
2007-06-24 20:10 ` Paul Brook
-- strict thread matches above, loose matches on Subject: below --
2007-06-22 5:34 Balazs Attila-Mihaly (Cd-MaN)
2007-06-22 15:21 ` Luke -Jr
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=200706221018.01516.luke@dashjr.org \
--to=luke@dashjr.org \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).