qemu-devel
[Top][All Lists]
Advanced

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

Re: [Qemu-devel] [PATCH] Mark future contributions to GPLv2-only files a


From: Kevin Wolf
Subject: Re: [Qemu-devel] [PATCH] Mark future contributions to GPLv2-only files as GPLv2+
Date: Fri, 21 Oct 2011 16:31:47 +0200
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:7.0) Gecko/20110927 Thunderbird/7.0

Am 21.10.2011 16:11, schrieb Anthony Liguori:
> On 10/21/2011 09:03 AM, Paolo Bonzini wrote:
>> Even for files are licensed GPLv2-only, let's not play catch with
>> ourselves, and explicitly declare that future contributions to those
>> files will also be available as "any later version".
>>
>> Signed-off-by: Paolo Bonzini<address@hidden>
>> diff --git a/roms/SLOF b/roms/SLOF
>> index d1d6b53..b94bde0 160000
>> --- a/roms/SLOF
>> +++ b/roms/SLOF
>> @@ -1 +1 @@
>> -Subproject commit d1d6b53b713a2b7c2c25685268fa932d28a4b4c0
>> +Subproject commit b94bde008b0d49ec4bfe933e110d0952d032ac28
> 
> I think you made a mistake here.
> 
> Otherwise I'm a bit concerned about ambiguity here.  Let's say we have to 
> backport a fit to stable, we need to pull in this new copyright statement.
> 
> But then what if we later discovered we need to pull in a fix from before 
> 10/25. 
>   That will appear in the stable tree as a post-10/25 commit but it carries a 
> GPLv2 only license.
> 
> I think a per-file flag day is really the only sane approach to this.

I don't think any part of this patch should be pulled into stable. When
backporting a new fix (which is basically dual GPLv2 and GPLv3), we can
choose which of the offered licenses to use. IANAL, but nothing should
stop us from only taking the GPLv2 option.

Am I misunderstanding something here?

Kevin



reply via email to

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