qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "andrzej zaborowski" <balrogg@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [patch] s390-dis.c license
Date: Fri, 18 Jan 2008 00:19:03 +0100	[thread overview]
Message-ID: <fb249edb0801171519s3ef79a56i9b38c11f9836df43@mail.gmail.com> (raw)
In-Reply-To: <20080117223145.GI28842@networkno.de>

On 17/01/2008, Thiemo Seufer <ths@networkno.de> wrote:
> andrzej zaborowski wrote:
> > On 17/01/2008, Bill C. Riemers <docbill@gmail.com> wrote:
> > > According to section 9 of the GPL, you would only have to contact
> > > contributors for code which specified version 2 of the GPL and not later...
> >
> > In order to relicense all of qemu, yes, plus contributors of
> > BSD-licensed code, of which there is much more than GPLv2-licensed.
>
> Actually, re-licensing BSD code as GPL is legal (but not nice).
>
> > But there's no reason to relicense qemu. AFAIK there's no problem
> > distributing qemu if it contains GPLv3, GPLv2 and BSD code just as
> > there was no problem until now with GPLv2 and BSD code. So I'm not
> > sure what this change helps.
>
> GPLv2 and GPLv3 have different provisions (e.g. the anti-DRM clause
> in GPLv3). Both exclude further restrictions of any sort. This makes
> them incompatible.

Ouch, right - I should do my reading. However the conflict between the
GPL versions might only restrict the distribution of a qemu binary.
And incorrect relicensing of the code would be illegal already in
source form.

So yes, probably only the GPLv2-only code would need permissions from
authors, BSD should be ok left intact. All LGPL code seems to be v2 or
greater.
Regards

  parent reply	other threads:[~2008-01-17 23:19 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-17 12:55 [Qemu-devel] [patch] s390-dis.c license Ulrich Hecht
2008-01-17 18:39 ` Stefan Weil
2008-01-17 18:45   ` M. Warner Losh
2008-01-17 18:55   ` Johannes Schindelin
2008-01-17 20:44     ` Ricardo Almeida
2008-01-17 21:07       ` M. Warner Losh
2008-01-17 21:29         ` Bill C. Riemers
2008-01-17 21:39           ` andrzej zaborowski
2008-01-17 22:31             ` Thiemo Seufer
2008-01-17 22:36               ` M. Warner Losh
2008-01-17 22:51                 ` Johannes Schindelin
2008-01-17 22:58                   ` M. Warner Losh
2008-01-17 22:56                 ` Thiemo Seufer
2008-01-17 23:19               ` andrzej zaborowski [this message]
2008-01-17 21:44           ` M. Warner Losh
2008-01-17 22:11             ` Thiemo Seufer
2008-01-17 22:09       ` Thiemo Seufer

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=fb249edb0801171519s3ef79a56i9b38c11f9836df43@mail.gmail.com \
    --to=balrogg@gmail.com \
    --cc=qemu-devel@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).