From: Stefan Weil <sw@weilnetz.de>
To: malc <av1474@comtv.ru>
Cc: Peter Maydell <peter.maydell@linaro.org>,
Anthony Liguori <aliguori@us.ibm.com>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] LICENSE: clarify licensing
Date: Mon, 19 Nov 2012 20:08:56 +0100 [thread overview]
Message-ID: <50AA83C8.4030402@weilnetz.de> (raw)
In-Reply-To: <alpine.LNX.2.00.1211192234380.5399@linmac>
Am 19.11.2012 19:34, schrieb malc:
> On Mon, 19 Nov 2012, Peter Maydell wrote:
>
>> On 19 November 2012 18:21, malc<av1474@comtv.ru> wrote:
>>> On Mon, 19 Nov 2012, Anthony Liguori wrote:
>>>> +5) Files without explicit licenses fall under the GPL v2.
>>>
>>> I have issue with this, files without licenses are just that files
>>> without licenses.
>>
>> If we believe this (and it seems a logical thing to believe)
>> then QEMU's not distributable until we rewrite or remove or track
>> down all authors for all the files without licenses...
>
> Yes.
That can only be true if those files are older than LICENSE,
or at least older than the commit which added
"QEMU as a whole is released under the GNU General Public License". (2007)
Any file or contribution which was added later (with or without a
license clause)
cannot invalidate this general license, so QEMU remains distributable.
Nevertheless fixing files without explicit license is desirable,
of course.
Stefan
next prev parent reply other threads:[~2012-11-19 19:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-19 16:40 [Qemu-devel] [PATCH] LICENSE: clarify licensing Anthony Liguori
2012-11-19 18:14 ` Paolo Bonzini
2012-11-19 18:21 ` malc
2012-11-19 18:34 ` Peter Maydell
2012-11-19 18:34 ` malc
2012-11-19 19:08 ` Stefan Weil [this message]
2012-11-19 19:30 ` malc
2012-11-19 19:48 ` Anthony Liguori
2012-11-19 20:00 ` malc
2012-11-20 10:39 ` Markus Armbruster
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=50AA83C8.4030402@weilnetz.de \
--to=sw@weilnetz.de \
--cc=aliguori@us.ibm.com \
--cc=av1474@comtv.ru \
--cc=peter.maydell@linaro.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).