qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] [RFC] introduce a dynamic library to expose qemu block


From: Lluís Vilanova
Subject: Re: [Qemu-devel] [RFC] introduce a dynamic library to expose qemu block API
Date: Mon, 23 Jul 2012 14:55:38 +0300
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/24.1.50 (gnu/linux)

Stefan Hajnoczi writes:
[...]
>> > So I tried trimming down the list of files needed to compile
>> > qemu tools, and here is a list:
>> 
>> > Easy to relicense to LGPLv2+:
>> > block/raw.c                     none (GPLv2+: Red Hat, IBM)
>> > error.c                         LGPLv2 (Red Hat, IBM, Stefan Weil)
>> > iov.c                           GPLv2 (Red Hat, SuSE/Hannes Reinecke, 
>> > Michael Tokarev)
>> > module.c                        GPLv2 (Red Hat, IBM, Blue Swirl)
>> > qemu-error.c                    GPLv2+ (Red Hat, Blue Swirl, IBM)
>> > trace/control.c                 GPLv2 (Lluis Vilanova)
>> > trace/default.c                 GPLv2 (Lluis Vilanova)
>> 
>> > (I added some people to Cc.  Lluis and Michael, can you also look at
>> > http://wiki.qemu.org/Relicensing if you're willing to relicense
>> > your past contributions from GPLv2 to GPLv2+?.  Blue Swirl said 
>> > he'd accept any other GPLv2 or GPLv3 compatible license, which
>> > should include LGPLv2+).
>> 
>> I have no problems relicensing to "GPLv2 or later" or "GPLv3 or later".

> What about LGPLv2+?  (Note the "L".)

I'd prefer to keep it non-lesser. Is it absolutely necessary?


PS: I suppose the "+" stands for "or later"

Lluis

-- 
 "And it's much the same thing with knowledge, for whenever you learn
 something new, the whole world becomes that much richer."
 -- The Princess of Pure Reason, as told by Norton Juster in The Phantom
 Tollbooth



reply via email to

[Prev in Thread] Current Thread [Next in Thread]