From: Eric Blake <eblake@redhat.com>
To: Programmingkid <programmingkidx@gmail.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
Gerd Hoffmann <kraxel@redhat.com>,
qemu-devel qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH v3 1/4] adb-keys.h: initial commit
Date: Mon, 7 Mar 2016 14:44:22 -0700 [thread overview]
Message-ID: <56DDF636.6080402@redhat.com> (raw)
In-Reply-To: <84C47D09-643A-4B2E-9E97-19B249A67D96@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1143 bytes --]
On 03/07/2016 02:33 PM, Programmingkid wrote:
>> If you don't have a strong license preference, then there are plenty of
>> GPLv2+ files you can copy from:
>>
>> $ git grep -l 'GPL, version 2 or' | wc -l
>> 482
>
> Rather than place the whole license agreement in the file, could I just say this:
>
> This code is licensed under the GNU GPL v2.
No, because that is GPLv2-only, not GPLv2+. The "or later" clause is an
important distinction (it determines whether your code can be copied
into a GPLv3+ project), and we've declared that no new files should be
GPLv2-only unless they are copied from a pre-existing project (such as
the Linux kernel) under that restriction, so that at least the rest of
qemu is usable in GPLv3 (even while qemu itself must remain GPLv2).
But if you're asking if you can use the two-liner present in
block/null.c (among other places), sure:
* This work is licensed under the terms of the GNU GPL, version 2 or later.
* See the COPYING file in the top-level directory.
*/
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 604 bytes --]
prev parent reply other threads:[~2016-03-07 21:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-05 5:15 [Qemu-devel] [PATCH v3 1/4] adb-keys.h: initial commit Programmingkid
2016-03-06 0:02 ` Eric Blake
2016-03-06 0:06 ` Programmingkid
2016-03-06 20:35 ` Programmingkid
2016-03-07 21:10 ` Eric Blake
2016-03-07 21:33 ` Programmingkid
2016-03-07 21:44 ` Eric Blake [this message]
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=56DDF636.6080402@redhat.com \
--to=eblake@redhat.com \
--cc=kraxel@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=programmingkidx@gmail.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).