From: Alexey Kardashevskiy <aik@ozlabs.ru>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Alexander Graf <agraf@suse.de>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
Tom Musta <tmusta@us.ibm.com>,
Anthony Liguori <aliguori@amazon.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Michael Ranweiler <mranweil@us.ibm.com>,
Paul Mackerras <paulus@samba.org>
Subject: Re: [Qemu-devel] fpu/softfloat.c licensing
Date: Mon, 04 Aug 2014 14:55:03 +1000 [thread overview]
Message-ID: <53DF1227.5080101@ozlabs.ru> (raw)
In-Reply-To: <CAFEAcA9jKkLZPRwpGqN25M4=c-6AN6qOpQjNdd85SdQ3xbdJMg@mail.gmail.com>
On 06/03/2014 09:42 PM, Peter Maydell wrote:
> On 3 June 2014 12:38, Alexey Kardashevskiy <aik@ozlabs.ru> wrote:
>> On 06/03/2014 07:45 PM, Peter Maydell wrote:
>>> On 3 June 2014 04:52, Alexey Kardashevskiy <aik@ozlabs.ru> wrote:
>>>> Is there anything I can do to help with this? Chase someone down? :)
>>>
>>> Confirming that your lawyers are happy with the approach
>>> Anthony proposed to take to fixing this would probably
>>> be useful :-)
>>
>> Let me refresh. Anthony suggested this -
>> http://marc.info/?l=qemu-devel&m=136725946312880&w=4
>>
>> To complete this, we need ack from a lot of people and three of them (
>> Fabrice Bellard, Jocelyn Mayer, Thiemo Seufer) have not ack'ed yet so we
>> either have to revert their changes (mwahaha) or we are stuck here.
>
> Essentially, yes. In particular it's not clear to me
> exactly how "clean room" our reimplementation of the
> bits of code we need to revert and rewrite has to be.
>
> Also is it sufficient to say "I started with the -2a
> codebase and applied a lot of patches to it, and ended
> up with a git commit which looks like "just change the
> comment style", or does our git history really need to
> look like "remove the -2b code, apply the -2a code,
> reapply intervening changes"? The former has the
> benefit of not breaking bisection, but if you look
> at the commit it looks a bit odd that we can remove
> the -2b licensing taint without actually touching most
> of the lines of code in the files...
Our lawyers refused to provide any public advise on this :-/
Is that it, end of story? :)
--
Alexey
next prev parent reply other threads:[~2014-08-04 4:55 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-21 3:54 [Qemu-devel] fpu/softfloat.c licensing Alexey Kardashevskiy
2014-05-21 7:51 ` Paolo Bonzini
2014-05-21 7:55 ` Alexander Graf
2014-05-21 9:43 ` Markus Armbruster
2014-05-21 9:47 ` Peter Maydell
2014-05-21 9:53 ` Andreas Färber
2014-05-21 8:43 ` Alexey Kardashevskiy
2014-05-21 9:17 ` Peter Maydell
2014-05-21 9:25 ` Alexander Graf
2014-06-03 3:52 ` Alexey Kardashevskiy
2014-06-03 9:45 ` Peter Maydell
2014-06-03 11:38 ` Alexey Kardashevskiy
2014-06-03 11:42 ` Peter Maydell
2014-08-04 4:55 ` Alexey Kardashevskiy [this message]
2014-08-04 8:48 ` Peter Maydell
2014-08-04 10:37 ` Alexey Kardashevskiy
2014-08-04 11:12 ` Markus Armbruster
2014-08-04 11:14 ` Peter Maydell
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=53DF1227.5080101@ozlabs.ru \
--to=aik@ozlabs.ru \
--cc=agraf@suse.de \
--cc=aliguori@amazon.com \
--cc=mranweil@us.ibm.com \
--cc=paulus@samba.org \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=tmusta@us.ibm.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).