qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Andreas Färber" <afaerber@suse.de>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Alexander Graf <agraf@suse.de>,
	Alexey Kardashevskiy <aik@ozlabs.ru>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
	Markus Armbruster <armbru@redhat.com>,
	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: Wed, 21 May 2014 11:53:58 +0200	[thread overview]
Message-ID: <537C77B6.4090106@suse.de> (raw)
In-Reply-To: <CAFEAcA9jtZxnML_c5h8Mk4tJ681xjGOqVRMFAtwX9UmGxOAOAg@mail.gmail.com>

Am 21.05.2014 11:47, schrieb Peter Maydell:
> On 21 May 2014 10:43, Markus Armbruster <armbru@redhat.com> wrote:
>> Alexander Graf <agraf@suse.de> writes:
>>> How many % of the overall commits does that make? IIRC you can
>>> relicense source code if the "majority of authors" agrees and nobody
>>> actively disagrees - or so. But IANAL :)
>>
>> You can get away with infringing copyright if nobody actively sues you.
>>
>> Sorry, not an option.  We have to rip out contributions we can't get
>> relicensed.  Except for contributions that don't qualify for copyright
>> protection, but that's shaky ground; let's not go there.
> 
> Presumably if IBM has an active interest in helping us to fix this
> they can provide an actual lawyer's legal opinion, so we don't
> need to make amateur guesses about what we need to do...

Well, in a previous case, IBM's legal department didn't manage to
relicense trivial malloc -> g_malloc changes by Anthony, so I wouldn't
set my hopes too high... confirming that relicensing someone's
contribution without their consent was not an option so far.

Cheers,
Andreas

-- 
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg

  reply	other threads:[~2014-05-21  9:54 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 [this message]
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
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=537C77B6.4090106@suse.de \
    --to=afaerber@suse.de \
    --cc=agraf@suse.de \
    --cc=aik@ozlabs.ru \
    --cc=aliguori@amazon.com \
    --cc=armbru@redhat.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).