From: Thomas Huth <thuth@redhat.com>
To: "Philippe Mathieu-Daudé" <philmd@redhat.com>,
qemu-devel@nongnu.org, "Daniel P. Berrangé" <berrange@redhat.com>
Cc: qemu-trivial@nongnu.org
Subject: Re: [Qemu-trivial] [Qemu-devel] [PATCH] crypto: Fix LGPL information in the file headers
Date: Wed, 13 Feb 2019 19:30:43 +0100 [thread overview]
Message-ID: <9518f0a6-2a89-ab4f-a431-d4e4741db8e5@redhat.com> (raw)
In-Reply-To: <1cbe8721-ea9e-f17f-f27d-910fece2858d@redhat.com>
On 2019-02-13 17:24, Philippe Mathieu-Daudé wrote:
> On 2/13/19 4:54 PM, Thomas Huth 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.
>>
>> Signed-off-by: Thomas Huth <thuth@redhat.com>
>> ---
>> crypto/block-luks.c | 2 +-
>> crypto/block-luks.h | 2 +-
>> crypto/block-qcow.c | 2 +-
>> crypto/block-qcow.h | 2 +-
>> crypto/block.c | 2 +-
>> crypto/blockpriv.h | 2 +-
>> crypto/cipher-builtin.c | 2 +-
>> crypto/cipher-gcrypt.c | 2 +-
>> crypto/cipher-nettle.c | 2 +-
>> crypto/cipher.c | 2 +-
>> crypto/hash-gcrypt.c | 2 +-
>> crypto/hash-glib.c | 2 +-
>> crypto/hash-nettle.c | 2 +-
>> crypto/hash.c | 2 +-
>> crypto/init.c | 2 +-
>> crypto/ivgen-essiv.c | 2 +-
>> crypto/ivgen-essiv.h | 2 +-
>> crypto/ivgen-plain.c | 2 +-
>> crypto/ivgen-plain.h | 2 +-
>> crypto/ivgen-plain64.c | 2 +-
>> crypto/ivgen-plain64.h | 2 +-
>> crypto/ivgen.c | 2 +-
>> crypto/ivgenpriv.h | 2 +-
>> crypto/pbkdf-gcrypt.c | 2 +-
>> crypto/pbkdf-nettle.c | 2 +-
>> crypto/pbkdf-stub.c | 2 +-
>> crypto/pbkdf.c | 2 +-
>> crypto/random-gcrypt.c | 2 +-
>> crypto/random-gnutls.c | 2 +-
>> crypto/random-platform.c | 2 +-
>> crypto/secret.c | 2 +-
>> crypto/tlscreds.c | 2 +-
>> crypto/tlscredsanon.c | 2 +-
>> crypto/tlscredspriv.h | 2 +-
>> crypto/tlscredspsk.c | 2 +-
>> crypto/tlscredsx509.c | 2 +-
>> crypto/tlssession.c | 2 +-
>> crypto/xts.c | 2 +-
>> include/crypto/block.h | 2 +-
>> include/crypto/cipher.h | 2 +-
>> include/crypto/hash.h | 2 +-
>> include/crypto/init.h | 2 +-
>> include/crypto/ivgen.h | 2 +-
>> include/crypto/pbkdf.h | 2 +-
>> include/crypto/random.h | 2 +-
>> include/crypto/secret.h | 2 +-
>> include/crypto/tlscreds.h | 2 +-
>> include/crypto/tlscredsanon.h | 2 +-
>> include/crypto/tlscredspsk.h | 2 +-
>> include/crypto/tlscredsx509.h | 2 +-
>> include/crypto/tlssession.h | 2 +-
>> include/crypto/xts.h | 2 +-
>> 52 files changed, 52 insertions(+), 52 deletions(-)
>
> Still not convinced to use SPDX-License-Identifiers?
SPDX sounds fine to me personally, but so far nobody came up with a
proper official description if and how this can legally be done, so
until we are at that point, fixing the current statements sounds like
the best solution to me.
Thomas
next prev parent reply other threads:[~2019-02-13 18:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-13 15:54 [Qemu-trivial] [PATCH] crypto: Fix LGPL information in the file headers Thomas Huth
2019-02-13 16:24 ` [Qemu-trivial] [Qemu-devel] " Philippe Mathieu-Daudé
2019-02-13 18:30 ` Thomas Huth [this message]
2019-05-10 15:50 ` [Qemu-trivial] " Daniel P. Berrangé
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=9518f0a6-2a89-ab4f-a431-d4e4741db8e5@redhat.com \
--to=thuth@redhat.com \
--cc=berrange@redhat.com \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@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).