From: "M. Warner Losh" <imp@bsdimp.com>
To: qemu-devel@nongnu.org, weil@mail.berlios.de
Subject: Re: [Qemu-devel] [patch] s390-dis.c license
Date: Thu, 17 Jan 2008 11:45:10 -0700 (MST) [thread overview]
Message-ID: <20080117.114510.179959847.imp@bsdimp.com> (raw)
In-Reply-To: <478FA0C9.8070907@mail.berlios.de>
In message: <478FA0C9.8070907@mail.berlios.de>
Stefan Weil <weil@mail.berlios.de> writes:
: Is GPLv3 unwanted for QEMU source code? If yes: why?
: Would it prevent inclusion of QEMU in common Linux distributions?
There's still some gplv2-only code in qemu, iirc. As such, you can't
use gplv3 code at all since the licenses are incompatible.
gplv2-or-later is not a problem.
I seriously doubt it would prevent being included in linux
distributions. The linux kernel, the thing that everybody says makes
linux linux, is gplv2-only right now.
Warner
: Stefan
:
: Ulrich Hecht schrieb:
: > Hi!
: >
: > Our Teenage Mutant Legal Turtles have discovered that s390-dis.c contains
: > GPLv3 code. Fortunately, the actual code has not changed since the last
: > GPLv2 binutils release, save for the license headers, so it suffices to
: > change those back to fix the problem.
: >
: > CU
: > Uli
:
:
:
next prev parent reply other threads:[~2008-01-17 18:48 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-17 12:55 [Qemu-devel] [patch] s390-dis.c license Ulrich Hecht
2008-01-17 18:39 ` Stefan Weil
2008-01-17 18:45 ` M. Warner Losh [this message]
2008-01-17 18:55 ` Johannes Schindelin
2008-01-17 20:44 ` Ricardo Almeida
2008-01-17 21:07 ` M. Warner Losh
2008-01-17 21:29 ` Bill C. Riemers
2008-01-17 21:39 ` andrzej zaborowski
2008-01-17 22:31 ` Thiemo Seufer
2008-01-17 22:36 ` M. Warner Losh
2008-01-17 22:51 ` Johannes Schindelin
2008-01-17 22:58 ` M. Warner Losh
2008-01-17 22:56 ` Thiemo Seufer
2008-01-17 23:19 ` andrzej zaborowski
2008-01-17 21:44 ` M. Warner Losh
2008-01-17 22:11 ` Thiemo Seufer
2008-01-17 22:09 ` Thiemo Seufer
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=20080117.114510.179959847.imp@bsdimp.com \
--to=imp@bsdimp.com \
--cc=qemu-devel@nongnu.org \
--cc=weil@mail.berlios.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.