From: Auke Kok <sofar@foo-projects.org>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] why is kqemu closed?
Date: Mon, 10 Apr 2006 15:47:18 +0000 [thread overview]
Message-ID: <3ef9fbda81a71790b3cc0575ebf95538@localhost> (raw)
In-Reply-To: <41e41e7a0604100820y3a20e731n4fb22e14db01e54e@mail.gmail.com>
On Mon, 10 Apr 2006 17:20:54 +0200, "Hetz Ben Hamo" <hetzbh@gmail.com> wrote:
> Fabrice is the owner of the KQEMU code, and he decides for his own
> reasons to put the code under closed source license.
I'm sure that Fabrice knows and that I'm beating a dead horse, but this is (strictly speaking, discussions pending ;^)) violating the linux kernel license agreement.
Auke
next prev parent reply other threads:[~2006-04-10 15:47 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-10 15:16 [Qemu-devel] why is kqemu closed? Rakotomandimby Mihamina
2006-04-10 15:20 ` Hetz Ben Hamo
2006-04-10 15:47 ` Auke Kok [this message]
2006-04-10 15:55 ` Hetz Ben Hamo
2006-04-10 15:56 ` Leonardo E. Reiter
2006-04-11 4:37 ` Auke Kok
2006-04-11 7:58 ` Brad Campbell
2006-04-11 16:22 ` Jim C. Brown
2006-04-11 8:37 ` Ricardo Almeida
2006-04-11 9:46 ` Johannes Schindelin
2006-04-11 10:05 ` Jamie Lokier
2006-04-11 15:05 ` Leonardo E. Reiter
2006-04-11 15:14 ` Jonas Maebe
2006-04-11 15:25 ` Jim C. Brown
2006-04-11 16:04 ` Jonas Maebe
2006-04-11 15:36 ` Paul Brook
2006-04-11 15:43 ` M. Warner Losh
2006-04-11 16:00 ` Paul Brook
2006-04-11 16:29 ` M. Warner Losh
2006-04-11 16:09 ` Jim C. Brown
2006-04-11 17:10 ` Enough already! " Bakul Shah
2006-04-11 15:17 ` Sebastian Kaliszewski
2006-04-11 15:31 ` M. Warner Losh
2006-04-11 12:33 ` andrzej zaborowski
2006-04-11 13:58 ` Jamie Lokier
2006-04-11 15:10 ` Sebastian Kaliszewski
2006-04-11 15:19 ` M. Warner Losh
2006-04-10 15:57 ` Brett (Mare) Henley
2006-04-10 16:02 ` Leonardo E. Reiter
2006-04-10 19:11 ` M. Warner Losh
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=3ef9fbda81a71790b3cc0575ebf95538@localhost \
--to=sofar@foo-projects.org \
--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).