From: Eric Blake <eblake@redhat.com>
To: Cornelia Huck <cohuck@redhat.com>, Thomas Huth <thuth@redhat.com>
Cc: qemu-trivial@nongnu.org, qemu-s390x@nongnu.org, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] target/s390x: Fix LGPL version in the file header comments
Date: Wed, 30 Jan 2019 09:01:01 -0600 [thread overview]
Message-ID: <e3dfae55-8733-bd01-1f13-422f343fb258@redhat.com> (raw)
In-Reply-To: <20190129145156.6719b8a4.cohuck@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 942 bytes --]
On 1/29/19 7:51 AM, Cornelia Huck wrote:
> On Tue, 29 Jan 2019 14:37:47 +0100
> Thomas Huth <thuth@redhat.com> wrote:
>
>> It's either "GNU *Library* General Public License version 2" or
>> "GNU Lesser General Public License version *2.1*", but there was
>> no "version 2.0" of the "Lesser" license. So assume that version
>> 2.1 is meant here.
>
> I think we can assume that.
>
> Given that there have been several of these cases (and that there's a
> lot of boilerplate in general): Should we adopt SPDX license
> identifiers for QEMU, as the Linux kernel did? They also discovered and
> fixed some problems/oddities while at it.
I'm also in favor of SPDX license identifiers - their brevity and
machine-parsability favors more accurate usage and fewer copy/paste
mistake propagation.
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3226
Virtualization: qemu.org | libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2019-01-30 15:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-29 13:37 [Qemu-devel] [PATCH] target/s390x: Fix LGPL version in the file header comments Thomas Huth
2019-01-29 13:51 ` Cornelia Huck
2019-01-29 15:05 ` Philippe Mathieu-Daudé
2019-01-30 15:01 ` Eric Blake [this message]
2019-01-30 15:18 ` Daniel P. Berrangé
2019-01-30 15:47 ` Cornelia Huck
2019-01-31 21:55 ` Richard Henderson
2019-01-30 10:04 ` [Qemu-devel] [Qemu-trivial] " Laurent Vivier
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=e3dfae55-8733-bd01-1f13-422f343fb258@redhat.com \
--to=eblake@redhat.com \
--cc=cohuck@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.org \
--cc=qemu-trivial@nongnu.org \
--cc=thuth@redhat.com \
/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).