From: Stefan Weil <sw@weilnetz.de>
To: Erik de Castro Lopo <mle+tools@mega-nerd.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Licensing question
Date: Wed, 31 Jul 2013 07:19:03 +0200 [thread overview]
Message-ID: <51F89E47.4000500@weilnetz.de> (raw)
In-Reply-To: <20130731115034.ef51e9eec58c6a691f6c9ae7@mega-nerd.com>
Am 31.07.2013 03:50, schrieb Erik de Castro Lopo:
> Hi all,
>
> I have a patch I would like to submit and I am currently running it past
> my employer's legal department. The legal department has identified 10
> different licenses in the Qemu codebase and has asked about the two files
> I am modifying:
>
> linux-user/syscall.c
> linux-user/syscall_defs.h
>
> For the first its easy as it is clearly marked as GPLv2+. The second is
> unmarked. Is there some blanket statement somewhere that all files that
> are not explicitly marked are under say GPLv2+?
>
> Cheers,
> Erik
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).
Regards,
Stefan
next prev parent reply other threads:[~2013-07-31 5:40 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 [this message]
2013-07-31 5:45 ` Erik de Castro Lopo
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=51F89E47.4000500@weilnetz.de \
--to=sw@weilnetz.de \
--cc=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 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.