qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Richard Henderson <richard.henderson@linaro.org>
To: Peter Maydell <peter.maydell@linaro.org>, qemu-devel@nongnu.org
Cc: Paolo Bonzini <pbonzini@redhat.com>,
	Stefan Hajnoczi <stefanha@redhat.com>,
	Markus Armbruster <armbru@redhat.com>,
	Claudio Fontana <claudio.fontana@gmail.com>
Subject: Re: [PATCH] tcg/LICENSE: Remove no-longer-true statement that TCG is BSD-licensed
Date: Mon, 21 Oct 2019 09:26:36 -0700	[thread overview]
Message-ID: <155991c2-523f-0721-c7a8-4fbe4986387c@linaro.org> (raw)
In-Reply-To: <06e15851-0b4e-63c3-001d-dd7ea5855872@linaro.org>

On 10/21/19 8:52 AM, Richard Henderson wrote:
> On 10/21/19 7:58 AM, Peter Maydell wrote:
>> Since 2008 the tcg/LICENSE file has not changed: it claims that
>> everything under tcg/ is BSD-licensed.
>>
>> This is not true and hasn't been true for years: in 2013 we
>> accepted the tcg/aarch64 target code under a GPLv2-or-later
>> license statement. We don't really consider the tcg
>> subdirectory to be a distinct part of QEMU anyway.
>>
>> Remove the LICENSE file, since claiming false information
>> about the license of the code is confusing, and update
>> the main project LICENSE file also to be clearer about
>> the license used by TCG.
>>
>> Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
>> ---
>> This patch takes the simple approach of just documenting
>> the de-facto current reality; does anybody want to argue
>> for something else? Other possibilities I guess would be
>> specifically documenting tcg/aarch64 as an accidental
>> exception to the general licensing rule for tcg/, or even
>> trying to get it relicensed.
>>
>> Does having tcg/ be BSD-licensed gain the project anything?
>> From my point of view I don't really see it as a cleanly
>> separable module of code -- it's quite tightly integrated
>> with the rest of QEMU, including code in accel/tcg which
>> is variously GPL or LGPL.
> 
> I think this is the best solution.  I've never been convinced that TCG can
> usefully be extracted and reused for something else.
> 
> Reviewed-by: Richard Henderson <richard.henderson@linaro.org>

Queued to tcg-next, as I think there's a couple of other things pending.


r~


  reply	other threads:[~2019-10-21 16:32 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-21 14:58 [PATCH] tcg/LICENSE: Remove no-longer-true statement that TCG is BSD-licensed Peter Maydell
2019-10-21 15:19 ` Paolo Bonzini
2019-10-21 15:29   ` Peter Maydell
2019-10-21 15:52 ` Richard Henderson
2019-10-21 16:26   ` Richard Henderson [this message]
2019-10-21 16:27     ` Peter Maydell
2019-10-21 16:30       ` Peter Maydell
2019-10-21 17:57   ` Laszlo Ersek
2019-10-21 19:52     ` Ard Biesheuvel
2019-10-22  5:21       ` Ard Biesheuvel
2019-10-21 16:36 ` Peter Maydell
2019-10-21 16:46   ` Daniel P. Berrangé
2019-10-21 16:55     ` Peter Maydell
2019-10-21 17:09       ` Paolo Bonzini

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=155991c2-523f-0721-c7a8-4fbe4986387c@linaro.org \
    --to=richard.henderson@linaro.org \
    --cc=armbru@redhat.com \
    --cc=claudio.fontana@gmail.com \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@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).