From: Anthony Liguori <anthony@codemonkey.ws>
To: qemu-devel@nongnu.org
Cc: xen-devel@lists.xensource.com, Gerd Hoffmann <kraxel@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 00/11] merge some xen bits into qemu
Date: Mon, 11 Aug 2008 12:11:41 -0500 [thread overview]
Message-ID: <48A072CD.8040608@codemonkey.ws> (raw)
In-Reply-To: <18592.28557.41406.258988@mariner.uk.xensource.com>
Ian Jackson wrote:
> Gerd Hoffmann writes ("[Qemu-devel] [PATCH 00/11] merge some xen bits into qemu"):
>
>> Comments?
>>
>
> Please do not apply these patches. They will make my life very
> difficult.
>
As I've said before, I won't apply these patches until there's agreement
that this is the right approach for QEMU and upstream Xen so no worries
there.
> If Gerd wants to rewrite the Xen/qemu support he should come to
> xen-devel and submit his patches there.
>
Actually, I think Gerd is taking the right approach. How Xen (and KVM
for that matter) integrates with QEMU is something that ought to be
discussed in both communities. That will make the long term merge
prospects easier. Working things out on xen-devel doesn't necessarily
mean you're any closer to getting into QEMU if qemu-devel has been left
out of the discussion.
Regards,
Anthony Liguori
> Ian.
>
>
>
next prev parent reply other threads:[~2008-08-11 17:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <m2n.s.1KSWf2-002Qtv@chiark.greenend.org.uk>
2008-08-11 16:57 ` [Qemu-devel] [PATCH 00/11] merge some xen bits into qemu Ian Jackson
2008-08-11 17:11 ` Anthony Liguori [this message]
2008-08-11 18:55 ` Blue Swirl
2008-08-12 10:04 ` Ian Jackson
2008-08-11 20:07 ` Gerd Hoffmann
2008-08-15 22:41 ` [Xen-devel] " Samuel Thibault
2008-08-18 12:45 ` Gerd Hoffmann
2008-08-18 12:53 ` Samuel Thibault
2008-08-18 13:29 ` Gerd Hoffmann
2008-08-11 12:32 Gerd Hoffmann
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=48A072CD.8040608@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=kraxel@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=xen-devel@lists.xensource.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).