From: "M. Warner Losh" <imp@bsdimp.com>
To: qemu-devel@nongnu.org, ric.almeida@gmail.com
Subject: Re: [Qemu-devel] [patch] s390-dis.c license
Date: Thu, 17 Jan 2008 14:07:06 -0700 (MST) [thread overview]
Message-ID: <20080117.140706.232931235.imp@bsdimp.com> (raw)
In-Reply-To: <8a6cde920801171244k35d84ec9vf82277d2e5090a4f@mail.gmail.com>
In message: <8a6cde920801171244k35d84ec9vf82277d2e5090a4f@mail.gmail.com>
"Ricardo Almeida" <ric.almeida@gmail.com> writes:
: > The problem is: you would have to ask every contributor whose code is
: > still somewhere in the source code. That is tedious, and takes time (I do
: > not even think that an email would suffice).
:
: >From what I read once in a slashdot post (it's worth what is worth),
: it suffices a public announcement of the change and a deadline
: (something around 60 to 90 days). The announce could be in QEmu
: homepage and on this list...
That's not legally correct. To change a license in a way not
permitted by the original license holder, you *MUST* have *EXPLICIT*
approval to do that. Otherwise, licenses would be meaningless...
Warner
next prev parent reply other threads:[~2008-01-17 21:09 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 [this message]
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
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.140706.232931235.imp@bsdimp.com \
--to=imp@bsdimp.com \
--cc=qemu-devel@nongnu.org \
--cc=ric.almeida@gmail.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).