From: Kevin Wolf <kwolf@redhat.com>
To: Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v3] qemu-iotests: add qed.py image manipulation utility
Date: Thu, 26 Jul 2012 14:31:21 +0200 [thread overview]
Message-ID: <50113899.9070301@redhat.com> (raw)
In-Reply-To: <1343305457-17446-1-git-send-email-stefanha@linux.vnet.ibm.com>
Am 26.07.2012 14:24, schrieb Stefan Hajnoczi:
> 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.
>
> This has lived in my local repo for a long time but could be useful
> to others.
>
> Signed-off-by: Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>
Thanks, applied to the block branch.
Kevin
next prev parent reply other threads:[~2012-07-26 12:32 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 [this message]
2012-07-26 12:56 ` Eric Blake
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=50113899.9070301@redhat.com \
--to=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.