From: Eric Blake <eblake@redhat.com>
To: Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>
Cc: Kevin Wolf <kwolf@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v3] qemu-iotests: add qed.py image manipulation utility
Date: Thu, 26 Jul 2012 06:56:11 -0600 [thread overview]
Message-ID: <50113E6B.9040202@redhat.com> (raw)
In-Reply-To: <1343305457-17446-1-git-send-email-stefanha@linux.vnet.ibm.com>
[-- Attachment #1: Type: text/plain, Size: 917 bytes --]
On 07/26/2012 06:24 AM, Stefan Hajnoczi wrote:
> The qed.py utility can inspect and manipulate QED image files. It can
> be used for testing to see the state of image metadata and also to
> inject corruptions into the image file. It also has a scrubbing feature
> to copy just the metadata out of an image file, allowing users to share
> broken image files without revealing data in bug reports.
>
> +# Copyright (C) 2010 IBM, Corp.
> +#
> +# Authors:
> +# Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>
> +#
> +# This work is licensed under the terms of the GNU GPL, version 2. See
> +# the COPYING file in the top-level directory.
On 07/26/2012 06:31 AM, Kevin Wolf wrote:> Am 26.07.2012 14:24, schrieb
> Thanks, applied to the block branch.
Is it too late to amend to GPLv2+?
--
Eric Blake eblake@redhat.com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 620 bytes --]
next prev parent reply other threads:[~2012-07-26 12:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-26 12:24 [Qemu-devel] [PATCH v3] qemu-iotests: add qed.py image manipulation utility Stefan Hajnoczi
2012-07-26 12:31 ` Kevin Wolf
2012-07-26 12:56 ` Eric Blake [this message]
2012-07-26 13:01 ` Kevin Wolf
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=50113E6B.9040202@redhat.com \
--to=eblake@redhat.com \
--cc=kwolf@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@linux.vnet.ibm.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.