From: "M. Warner Losh" <imp@bsdimp.com>
To: Johannes.Schindelin@gmx.de
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [patch] s390-dis.c license
Date: Thu, 17 Jan 2008 15:58:31 -0700 (MST) [thread overview]
Message-ID: <20080117.155831.129710387.imp@bsdimp.com> (raw)
In-Reply-To: <alpine.LSU.1.00.0801172250060.5731@racer.site>
In message: <alpine.LSU.1.00.0801172250060.5731@racer.site>
Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
: Hi,
:
: On Thu, 17 Jan 2008, M. Warner Losh wrote:
:
: > In message: <20080117223145.GI28842@networkno.de>
: > Thiemo Seufer <ths@networkno.de> writes:
: > : 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).
: >
: > No. It isn't. *ADDING* the GPL license to a 2-clause BSD licensed file
: > is legal, but removing the BSD stuff is not allowed. It must be
: > retained, per the BSD license.
:
: Since we are in pea-counter mode: if you add something _more_ than just a
: license, you _can_ relicense with the GPL. That means that everybody
: using _your_ modified version as a base _must_ license the result using
: GPL, or not license it at all.
Almost right. They must license with the GPL, but the original BSD
license must also remain intact within the file. Since the GPL is a
supoerset of the 2-cluase BSD license, you are actually licensing
under both...
Warner
next prev parent reply other threads:[~2008-01-17 23:00 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 [this message]
2008-01-17 22:56 ` Thiemo Seufer
2008-01-17 23:19 ` andrzej zaborowski
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=20080117.155831.129710387.imp@bsdimp.com \
--to=imp@bsdimp.com \
--cc=Johannes.Schindelin@gmx.de \
--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).