qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: Jan Kiszka <jan.kiszka@web.de>
Cc: qemu-devel <qemu-devel@nongnu.org>,
	Luiz Capitulino <lcapitulino@redhat.com>
Subject: Re: [Qemu-devel] QLicense chaos
Date: Fri, 07 May 2010 19:05:42 -0500	[thread overview]
Message-ID: <4BE4AAD6.5020905@codemonkey.ws> (raw)
In-Reply-To: <4BE46C8A.2010002@web.de>

On 05/07/2010 02:39 PM, Jan Kiszka wrote:
> Hi guys,
>
> /*
>   * QFloat Module
>   *
>   * Copyright (C) 2009 Red Hat Inc.
>   *
>   * Authors:
>   *  Luiz Capitulino<lcapitulino@redhat.com>
>   *
>   * This work is licensed under the terms of the GNU GPL, version 2.  See
>   * the COPYING file in the top-level directory.
>   *
>   * Copyright IBM, Corp. 2009
>   *
>   * Authors:
>   *  Anthony Liguori<aliguori@us.ibm.com>
>   *
>   * This work is licensed under the terms of the GNU LGPL, version 2.1 or later.
>   * See the COPYING.LIB file in the top-level directory.
>   *
>   */
>
> Could you clean this up (and QBool)?
>
> Moreover, some of the QObject files are LGPL, some GPL. I bet this was
> also not intended. But what was the idea behind the LGPL? Some libqmp which
> can be used by closed source apps? Then better establish the required
> license soon. Postponing this will only once require tedious author
> questionings.
>    

So lgpl libraries (like libvirt) can use libqmp.

Regards,

Anthony Liguori

> Jan
>
>    

      parent reply	other threads:[~2010-05-08  0:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-07 19:39 [Qemu-devel] QLicense chaos Jan Kiszka
2010-05-07 19:56 ` [Qemu-devel] " Luiz Capitulino
2010-05-07 23:02 ` [Qemu-devel] " Jamie Lokier
2010-05-08  0:05 ` Anthony Liguori [this message]

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=4BE4AAD6.5020905@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --cc=jan.kiszka@web.de \
    --cc=lcapitulino@redhat.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).