From: "Andreas Färber" <afaerber@suse.de>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: qemu-devel@nongnu.org, Jason Douglas <JDOUGLAS@suse.com>
Subject: Re: [Qemu-devel] [PATCH v3] prepare for future GPLv2+ relicensing
Date: Fri, 13 Jan 2012 17:39:08 +0100 [thread overview]
Message-ID: <4F105E2C.40101@suse.de> (raw)
In-Reply-To: <1326471974-25351-1-git-send-email-pbonzini@redhat.com>
Am 13.01.2012 17:26, schrieb Paolo Bonzini:
> All files under GPLv2 will get GPLv2+ changes starting next Christmas.
> event_notifier.c and exec-obsolete.h were only ever touched by Red Hat
> employees and can be relicensed now.
"Next Christmas" vs. 2012-01-13 in the headers.
Thanks for adding the file names. Can't re-review all of it today.
Andreas
--
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
next prev parent reply other threads:[~2012-01-13 16:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-13 16:26 [Qemu-devel] [PATCH v3] prepare for future GPLv2+ relicensing Paolo Bonzini
2012-01-13 16:39 ` Andreas Färber [this message]
2012-01-13 16:44 ` [Qemu-devel] [PATCH v4] " Paolo Bonzini
2012-01-13 16:59 ` 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=4F105E2C.40101@suse.de \
--to=afaerber@suse.de \
--cc=JDOUGLAS@suse.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).