From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Cc: Anthony Liguori <aliguori@us.ibm.com>,
Ryan Harper <ryanh@us.ibm.com>,
kvm@vger.kernel.org
Subject: Re: [Qemu-devel] [PATCH 0/1] integrate qemu-test into kvm-userspace
Date: Fri, 25 Jul 2008 18:12:34 +0100 [thread overview]
Message-ID: <200807251812.34838.paul@codesourcery.com> (raw)
In-Reply-To: <1217004805-13955-1-git-send-email-ryanh@us.ibm.com>
> Ultimately, I'd like to push this into qemu since nothing we're doing
> here is arch or kvm specific.
What advantage does inclusion with qemu give?
AFAICS You're going to have to download gigabytes of images anyway, so
wouldn't it make more sense to include the test script with those?
Paul
next prev parent reply other threads:[~2008-07-25 17:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-25 16:53 [Qemu-devel] [PATCH 0/1] integrate qemu-test into kvm-userspace Ryan Harper
2008-07-25 16:53 ` [Qemu-devel] [PATCH 1/1] " Ryan Harper
2008-07-25 17:12 ` Paul Brook [this message]
2008-07-25 17:52 ` [Qemu-devel] [PATCH 0/1] " Anthony Liguori
2008-07-25 17:57 ` Ryan Harper
2008-07-29 13:17 ` [Qemu-devel] " Avi Kivity
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=200807251812.34838.paul@codesourcery.com \
--to=paul@codesourcery.com \
--cc=aliguori@us.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=qemu-devel@nongnu.org \
--cc=ryanh@us.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 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).