All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Artyom Tarasenko <atar4qemu@gmail.com>
Cc: "Anthony Liguori" <aliguori@us.ibm.com>,
	"Stefan Weil" <sw@weilnetz.de>,
	qemu-devel@nongnu.org, "Luiz Capitulino" <lcapitulino@redhat.com>,
	"Andreas Färber" <afaerber@suse.de>,
	"Markus Armbruster" <armbru@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] w32: Fix broken build (missing include file)
Date: Sun, 01 Jul 2012 16:26:17 +0200	[thread overview]
Message-ID: <4FF05E09.9070606@redhat.com> (raw)
In-Reply-To: <CACXAS8DPPb8pA5xJKTB+ci-cPWnExCBAcrezqUjeM9ubAzSjzA@mail.gmail.com>

Il 16/06/2012 20:48, Artyom Tarasenko ha scritto:
> But still, it's not possible for all contributions, right?
> 
> To sum this up:
> GPL v2+ are allowed
> non-GPL contributions are allowed

Yes, as long as they are GPLv2- and v3-compatible.  So for example no
Apache license (just a theoretical case, but worth mentioning for
completeness), because it's not GPLv2-compatible.

I'm not aware of any license that is GPLv2-compatible but not GPLv3, but
there must be one hiding somewhere. :)

Paolo

> GPL v2- are not allowed.

  reply	other threads:[~2012-07-01 14:26 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
2012-06-16 18:48           ` Artyom Tarasenko
2012-07-01 14:26             ` Paolo Bonzini [this message]
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=4FF05E09.9070606@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=afaerber@suse.de \
    --cc=aliguori@us.ibm.com \
    --cc=armbru@redhat.com \
    --cc=atar4qemu@gmail.com \
    --cc=lcapitulino@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.