From: Samuel Thibault <samuel.thibault@eu.citrix.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: xen-devel@lists.xensource.com, qemu-devel@nongnu.org
Subject: Re: [Xen-devel] Re: [Qemu-devel] [PATCH 00/11] merge some xen bits into qemu
Date: Fri, 15 Aug 2008 23:41:42 +0100 [thread overview]
Message-ID: <20080815224142.GF5198@implementation> (raw)
In-Reply-To: <48A09BEC.2040504@redhat.com>
Gerd Hoffmann, le Mon 11 Aug 2008 22:07:08 +0200, a écrit :
> 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.
>
> Go to http://kraxel.fedorapeople.org/patches/qemu-xen/. Apply the
> patches to your tree. Run them through the XenSource regression
> testing. Complain if I broke something. It can't be much easier than
> that for you.
Well, maybe having a version of the patch that does not convert the code
into the qemu identation would help a lot for on-list review.
Also, would it be possible to just have the backend core and
console+framebuffer patches alone? I don't see why we would need to
change xen_machine_pv.c at all.
That being said, I guess we should wait for a pull in the qemu-xen tree.
Samuel
WARNING: multiple messages have this Message-ID (diff)
From: Samuel Thibault <samuel.thibault@eu.citrix.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: xen-devel@lists.xensource.com, qemu-devel@nongnu.org
Subject: Re: Re: [Qemu-devel] [PATCH 00/11] merge some xen bits into qemu
Date: Fri, 15 Aug 2008 23:41:42 +0100 [thread overview]
Message-ID: <20080815224142.GF5198@implementation> (raw)
In-Reply-To: <48A09BEC.2040504@redhat.com>
Gerd Hoffmann, le Mon 11 Aug 2008 22:07:08 +0200, a écrit :
> 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.
>
> Go to http://kraxel.fedorapeople.org/patches/qemu-xen/. Apply the
> patches to your tree. Run them through the XenSource regression
> testing. Complain if I broke something. It can't be much easier than
> that for you.
Well, maybe having a version of the patch that does not convert the code
into the qemu identation would help a lot for on-list review.
Also, would it be possible to just have the backend core and
console+framebuffer patches alone? I don't see why we would need to
change xen_machine_pv.c at all.
That being said, I guess we should wait for a pull in the qemu-xen tree.
Samuel
next prev parent reply other threads:[~2008-08-15 22:41 UTC|newest]
Thread overview: 14+ 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
2008-08-11 18:55 ` Blue Swirl
2008-08-11 18:55 ` Blue Swirl
2008-08-12 10:04 ` [Qemu-devel] " Ian Jackson
2008-08-11 20:07 ` Gerd Hoffmann
2008-08-15 22:41 ` Samuel Thibault [this message]
2008-08-15 22:41 ` Samuel Thibault
2008-08-18 12:45 ` [Xen-devel] " Gerd Hoffmann
2008-08-18 12:45 ` Gerd Hoffmann
2008-08-18 12:53 ` [Xen-devel] " Samuel Thibault
2008-08-18 12:53 ` Samuel Thibault
2008-08-18 13:29 ` [Xen-devel] " Gerd Hoffmann
2008-08-18 13:29 ` 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=20080815224142.GF5198@implementation \
--to=samuel.thibault@eu.citrix.com \
--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 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.