qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Kevin Wolf <kwolf@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: blauwirbel@gmail.com, Paolo Bonzini <pbonzini@redhat.com>,
	qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] Mark future contributions to GPLv2-only files as GPLv2+
Date: Fri, 21 Oct 2011 16:31:47 +0200	[thread overview]
Message-ID: <4EA18253.7080505@redhat.com> (raw)
In-Reply-To: <4EA17D9D.5010801@codemonkey.ws>

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<pbonzini@redhat.com>
>> 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

  parent reply	other threads:[~2011-10-21 14:28 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-21 14:03 [Qemu-devel] [PATCH] Mark future contributions to GPLv2-only files as GPLv2+ Paolo Bonzini
2011-10-21 14:11 ` Anthony Liguori
2011-10-21 14:27   ` Paolo Bonzini
2011-10-21 14:31   ` Kevin Wolf [this message]
2011-12-12 16:36 ` Anthony Liguori
2011-12-12 21:35   ` Paolo Bonzini
2011-12-12 21:55     ` Anthony Liguori

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=4EA18253.7080505@redhat.com \
    --to=kwolf@redhat.com \
    --cc=anthony@codemonkey.ws \
    --cc=blauwirbel@gmail.com \
    --cc=pbonzini@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).