From: Laurent Vivier <laurent@vivier.eu>
To: Cornelia Huck <cohuck@redhat.com>, Thomas Huth <thuth@redhat.com>
Cc: qemu-devel@nongnu.org, qemu-s390x@nongnu.org,
Riku Voipio <riku.voipio@iki.fi>,
Christian Borntraeger <borntraeger@de.ibm.com>,
Alexander Graf <agraf@suse.de>
Subject: Re: [Qemu-devel] [PATCH] s390x: Fix the confusing contributions-after-2012 license statements
Date: Wed, 6 Feb 2019 14:02:25 +0100 [thread overview]
Message-ID: <52b3de29-6918-952d-9d91-abdfb6dba25b@vivier.eu> (raw)
In-Reply-To: <20190206135840.60a2a49f.cohuck@redhat.com>
On 06/02/2019 13:58, Cornelia Huck wrote:
> On Wed, 6 Feb 2019 13:41:33 +0100
> Thomas Huth <thuth@redhat.com> wrote:
>
>> The license information in these files is rather confusing. The text
>> declares LGPL first, but then says that contributions after 2012 are
>> licensed under the GPL instead. How should the average user who just
>> downloaded the release tarball know which part is now GPL and which
>> is LGPL?
>
> FWIW, that statement was added in ccb084d3f0ec ("s390: new
> contributions GPLv2 or later").
>
>>
>> Looking at the text of the LGPL (see COPYING.LIB in the top directory),
>> the license clearly states how this should be done instead:
>>
>> "3. You may opt to apply the terms of the ordinary GNU General Public
>> License instead of this License to a given copy of the Library. To do
>> this, you must alter all the notices that refer to this License, so
>> that they refer to the ordinary GNU General Public License, version 2,
>> instead of to this License."
>
> Hm. This talks about GPL v2, not GPL v2-or-later...
>
>>
>> Thus let's clean up the confusing statements and use the proper GPL
>> text only.
>>
>> Signed-off-by: Thomas Huth <thuth@redhat.com>
>> ---
>> linux-user/s390x/target_cpu.h | 19 ++++++++-----------
>> target/s390x/cpu.c | 19 ++++++++-----------
>> target/s390x/cpu.h | 19 ++++++++-----------
>> target/s390x/kvm.c | 19 ++++++++-----------
>
> BTW: Is the original author of the code still around?
For the linux-user/s390x/target_cpu.h, it seems this code has been pushed by Alex Graf:
commit 10ec51174ca69a4c3c5149b0b3baaa6ccba66273
Author: Alexander Graf <agraf@suse.de>
Date: Sat Dec 5 12:44:21 2009 +0100
S/390 CPU fake emulation
Because Qemu currently requires a TCG target to exist and there are quite some
useful helpers here to lay the groundwork for out KVM target, let's create a
stub TCG emulation target for S390X CPUs.
This is required to make tcg happy. The emulation target itself won't work
though.
Signed-off-by: Alexander Graf <agraf@suse.de>
Signed-off-by: Aurelien Jarno <aurelien@aurel32.net>
But the "(c) 2009 Ulrich Hecht" is confusing.
Laurent
next prev parent reply other threads:[~2019-02-06 13:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-06 12:41 [Qemu-devel] [PATCH] s390x: Fix the confusing contributions-after-2012 license statements Thomas Huth
2019-02-06 12:58 ` Cornelia Huck
2019-02-06 13:02 ` Laurent Vivier [this message]
2019-02-11 15:24 ` Alexander Graf
2019-02-11 15:31 ` Cornelia Huck
2019-02-11 16:00 ` Alexander Graf
2019-02-11 16:05 ` Cornelia Huck
2019-02-06 13:09 ` Thomas Huth
2019-02-06 13:15 ` Cornelia Huck
2019-02-06 13:17 ` Laurent Vivier
2019-02-06 14:28 ` [Qemu-devel] [qemu-s390x] " Christian Borntraeger
2019-02-11 10:43 ` [Qemu-devel] " Cornelia Huck
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=52b3de29-6918-952d-9d91-abdfb6dba25b@vivier.eu \
--to=laurent@vivier.eu \
--cc=agraf@suse.de \
--cc=borntraeger@de.ibm.com \
--cc=cohuck@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.org \
--cc=riku.voipio@iki.fi \
--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).