qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "John R. Hogerhuis" <jhoger@pobox.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Re: Sponsorship for QEMU Developers...
Date: Sun, 06 Mar 2005 01:01:23 -0800	[thread overview]
Message-ID: <1110099683.12889.47.camel@aragorn> (raw)
In-Reply-To: <422A97C9.5090004@win4lin.com>

On Sun, 2005-03-06 at 00:40 -0500, Leonardo E. Reiter wrote:
> Hi John,
> 
> I apologize for any confusion.  In fact I think I also used 'GPL' in my 
> note by mistake instead of 'LGPL'.
> 

Yep, noticed that. But I was still wrong. I just can't keep QEMU
licensing straight in my head. Maybe now that I stepped in it good, I'll
remember ;-) QEMU is LGPL or BSD. 

> The bottom line is just that we always prefer to err on the safe side, 
> thus we chose not to include files such as 'vl.h' in our closed source 
> bits.  Plus, it can get a bit dicey when the same tarball actually 
> contains code with 2 or 3 (most files have BSD-style licenses in their 
> comment headers!) types of licenses.  It was just the safe thing to do 
> from our perspective, even if we were not even enabling the GPL'd code.
> 

I suppose. But if its LGPL and Fabrice is amenable, it would seem you're
safe enough, particularly if you get something confirming your
interpretation from Fabrice. Then you get rid of any kind of overhead or
maintainability issues from your dynamic linking code.

> If you or anyone else has any other questions about how we interact with 
> QEMU in our Win4Lin Pro product, please ask.  I want to be as honest and 
> forward as possible with everyone, and hope that my company can work 
> together in harmony with this great QEMU community.
> 

More of an interesting intellectual excercise for me. That linking issue
just set off alarm bells in my head. But given LGPL or BSD everything
looks peachy.

> Thank you for your understanding,
> 

Thank you for taking an interest in sponsoring the work of QEMU
developers.

-- John.

  reply	other threads:[~2005-03-06  9:21 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-04 20:11 [Qemu-devel] Sponsorship for QEMU Developers Leonardo E. Reiter
2005-03-04 22:08 ` Paul Brook
2005-03-04 22:10   ` Leonardo E. Reiter
2005-03-04 23:45 ` Joshua Kugler
2005-03-04 23:57 ` Magnus Damm
2005-03-05 19:13 ` Marc Collin
2005-03-05 22:27   ` Leonardo E. Reiter
2005-03-06  1:51     ` [Qemu-devel] " Robert Wittams
2005-03-06  2:48       ` Leonardo E. Reiter
2005-03-06  3:32         ` John R. Hogerhuis
2005-03-06  3:47           ` Jim C. Brown
2005-03-06  4:37             ` John R. Hogerhuis
2005-03-06  5:40               ` Leonardo E. Reiter
2005-03-06  9:01                 ` John R. Hogerhuis [this message]
2005-03-06 11:42         ` Robert Wittams
2005-03-06  9:45       ` Jonas Maebe
2005-03-06 10:28         ` Jonas Maebe

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=1110099683.12889.47.camel@aragorn \
    --to=jhoger@pobox.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).