From: Stefan Weil <weil@mail.berlios.de>
To: Jan Kiszka <jan.kiszka@siemens.com>,
Anthony Liguori <aliguori@us.ibm.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
Christoph Egger <Christoph.Egger@amd.com>,
Eric Blake <eblake@redhat.com>, Alexander Graf <agraf@suse.de>,
qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] signrom: Rewrite as python script
Date: Tue, 24 Jan 2012 19:49:54 +0100 [thread overview]
Message-ID: <4F1EFD52.4070807@mail.berlios.de> (raw)
In-Reply-To: <4F1ECD52.4000701@siemens.com>
Am 24.01.2012 16:25, schrieb Jan Kiszka:
> On 2012-01-24 16:22, Eric Blake wrote:
>> On 01/24/2012 01:53 AM, Jan Kiszka wrote:
>>> Now that we have a hard dependency on python anyway, we can replace the
>>> slow shell script to calculate the option ROM checksum with a fast AND
>>> portable python version. Tested both with python 2.7 and 3.1.
>>>
>>> Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
>>> ---
>>>
>>> +++ b/scripts/signrom.py
>>> @@ -0,0 +1,40 @@
>>> +#
>>> +# Option ROM Signing utility
>>> +#
>>> +# Authors:
>>> +# Jan Kiszka <jan.kiszka@siemens.com>
>>> +#
>>> +# This work is licensed under the terms of the GNU GPLv2.
>>
>> Any reason you aren't using GPLv2+,
>
> Internal complications. :-/
Then I think these complications need to be handled first.
Any new code with GLP should use GPLv2+.
Can you use a BSD like license or PD?
Regards,
Stefan
PS. Anthony, there are more scripts/*.py files with GPLv2 only.
As they are all from IBM / Redhat / Blue, they can be changed to GPLv2+.
prev parent reply other threads:[~2012-01-24 18:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-24 8:53 [Qemu-devel] [PATCH] signrom: Rewrite as python script Jan Kiszka
2012-01-24 15:22 ` Eric Blake
2012-01-24 15:25 ` Jan Kiszka
2012-01-24 15:54 ` Markus Armbruster
2012-01-24 18:49 ` Stefan Weil [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=4F1EFD52.4070807@mail.berlios.de \
--to=weil@mail.berlios.de \
--cc=Christoph.Egger@amd.com \
--cc=agraf@suse.de \
--cc=aliguori@us.ibm.com \
--cc=eblake@redhat.com \
--cc=jan.kiszka@siemens.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).