From: "Andreas Färber" <afaerber@suse.de>
To: Artyom Tarasenko <atar4qemu@gmail.com>
Cc: Anthony Liguori <aliguori@us.ibm.com>,
Stefan Weil <sw@weilnetz.de>,
qemu-devel@nongnu.org, Markus Armbruster <armbru@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Luiz Capitulino <lcapitulino@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] w32: Fix broken build (missing include file)
Date: Sat, 16 Jun 2012 20:31:49 +0200 [thread overview]
Message-ID: <4FDCD115.80602@suse.de> (raw)
In-Reply-To: <CACXAS8CgsmQewDUWSMigCcjDmBV7Sakxd4Pfv14yE87-HTuKRA@mail.gmail.com>
Am 16.06.2012 20:07, schrieb Artyom Tarasenko:
> On 6/12/12, Markus Armbruster <armbru@redhat.com> wrote:
>> Paolo Bonzini <pbonzini@redhat.com> writes:
>>
>>> Il 11/06/2012 03:57, Wen Congyang ha scritto:
>>>>> dump.* use GPL2 instead of GPL2+. Please fix that!
>>>
>>> Wen, do you have permissions to release your new files under GPLv2 or
>>> later?
>>
>> Don't we require GPLv2+ for all contributions now? If not, we should.
>>
>
> I think it's not possible for all contributions.
[snip]
You're reading this out of context. It's about GPLv2 vs. GPLv2+, not
about GPL vs. BSD/MIT/...
Andreas
--
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
next prev parent reply other threads:[~2012-06-16 18:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-07 13:45 [Qemu-devel] [PATCH] w32: Fix broken build (missing include file) Stefan Weil
2012-06-09 11:28 ` Blue Swirl
2012-06-11 1:57 ` Wen Congyang
2012-06-11 4:58 ` Paolo Bonzini
2012-06-12 7:12 ` Markus Armbruster
2012-06-16 18:07 ` Artyom Tarasenko
2012-06-16 18:31 ` Andreas Färber [this message]
2012-06-16 18:48 ` Artyom Tarasenko
2012-07-01 14:26 ` Paolo Bonzini
2012-07-03 18:50 ` Blue Swirl
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=4FDCD115.80602@suse.de \
--to=afaerber@suse.de \
--cc=aliguori@us.ibm.com \
--cc=armbru@redhat.com \
--cc=atar4qemu@gmail.com \
--cc=lcapitulino@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=sw@weilnetz.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.