From: Blue Swirl <blauwirbel@gmail.com>
To: qemu-devel@nongnu.org, Anthony Liguori <aliguori@us.ibm.com>
Subject: Re: [Qemu-devel] [6990] qemu-io - an I/O path exerciser (Christoph Hellwig)
Date: Sun, 5 Apr 2009 22:17:07 +0300 [thread overview]
Message-ID: <f43fc5580904051217k291da257j15ff5bdc7ee401de@mail.gmail.com> (raw)
In-Reply-To: <E1LqXHX-0003br-FX@cvs.savannah.gnu.org>
On 4/5/09, Anthony Liguori <anthony@codemonkey.ws> wrote:
> Revision: 6990
> http://svn.sv.gnu.org/viewvc/?view=rev&root=qemu&revision=6990
> Author: aliguori
> Date: 2009-04-05 18:41:23 +0000 (Sun, 05 Apr 2009)
> Log Message:
> -----------
> qemu-io - an I/O path exerciser (Christoph Hellwig)
> Modified Paths:
> --------------
> trunk/Makefile
> trunk/configure
Forgot something?
prev parent reply other threads:[~2009-04-05 19:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-05 18:41 [Qemu-devel] [6990] qemu-io - an I/O path exerciser (Christoph Hellwig) Anthony Liguori
2009-04-05 19:17 ` Blue Swirl [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=f43fc5580904051217k291da257j15ff5bdc7ee401de@mail.gmail.com \
--to=blauwirbel@gmail.com \
--cc=aliguori@us.ibm.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).