qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Erik de Castro Lopo <mle+tools@mega-nerd.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Licensing question
Date: Wed, 31 Jul 2013 15:45:24 +1000	[thread overview]
Message-ID: <20130731154524.6ad18a2526dd573eade0857d@mega-nerd.com> (raw)
In-Reply-To: <51F89E47.4000500@weilnetz.de>

Stefan Weil wrote:

> No, there is no such statement.
> 
> There is an agreement that files with GPL should be GPLv2+
> (not only GPLv2), but files may also use other free licenses.
> 
> In file LICENSE, it is said that QEMU as a whole is released
> under the GNU General Public License.
> 
> Some files are copied from Linux and therefore must use
> the Linux license (usually GPLv2).
> 
> syscall_defs.h might be a copy from Linux (=> GPLv2).
> If not, the default rule from LICENSE could be applied (=> GPL).

Thanks Stefan.

The file does not seem to come from the linux kernel and google
found a bunch of other files with the same name, but they either
seemed to be un-related files (eg one from OpenBSD) or to be
dervied from this file in Qemu.

That means the file is under the default license for Qemu. The
LICENSE file simply says "GNU General Public License" without
specifying which version of that license. Does this mean GPLv2,
GPLv2+, GPL3 or GPLv3+?

Sorry about these annoying questions, but lawyers tend to be
sticklers for these minor details.

Cheer,
Erik
-- 
----------------------------------------------------------------------
Erik de Castro Lopo
http://www.mega-nerd.com/

  reply	other threads:[~2013-07-31  5:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-31  1:50 [Qemu-devel] Licensing question Erik de Castro Lopo
2013-07-31  5:19 ` Stefan Weil
2013-07-31  5:45   ` Erik de Castro Lopo [this message]
2013-07-31  6:20     ` Paolo Bonzini
2013-08-02 16:59   ` Rob Landley

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=20130731154524.6ad18a2526dd573eade0857d@mega-nerd.com \
    --to=mle+tools@mega-nerd.com \
    --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).