From: Christoph Egger <Christoph.Egger@amd.com>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: Ian, Campbell <Ian.Campbell@eu.citrix.com>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: [PATCH] ioemu: build fixes for netbsd packaging
Date: Tue, 24 May 2011 13:38:06 +0200 [thread overview]
Message-ID: <4DDB989E.4010609@amd.com> (raw)
In-Reply-To: <19931.36060.194462.581803@mariner.uk.xensource.com>
On 05/24/11 12:47, Ian Jackson wrote:
> Christoph Egger writes ("Re: [Xen-devel] [PATCH] ioemu: build fixes for netbsd packaging"):
>>
>> Ian Campbell: There is no response from Ian Jackson at all.
>> Can you commit it before Xen 4.1.1 release, please? Thanks.
>
> I'm afraid I've been putting off replying to you about this one. I
> think it's a pretty big and ugly patch. I would rather not make these
> kind of wholesale changes to the old qemu-xen at this point.
>
> This is particularly true given that this is now effectively a
> nearly-dead branch, which we will be maintaining for backward
> compatibility only.
Does that mean Xen 4.1.x will move to upstream qemu
along with xen-unstable?
Christoph
--
---to satisfy European Law for business letters:
Advanced Micro Devices GmbH
Einsteinring 24, 85689 Dornach b. Muenchen
Geschaeftsfuehrer: Alberto Bozzo, Andrew Bowd
Sitz: Dornach, Gemeinde Aschheim, Landkreis Muenchen
Registergericht Muenchen, HRB Nr. 43632
next prev parent reply other threads:[~2011-05-24 11:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-15 12:00 [PATCH] ioemu: build fixes for netbsd packaging Christoph Egger
2011-04-26 9:43 ` Christoph Egger
2011-05-18 8:34 ` Christoph Egger
2011-05-24 10:13 ` Christoph Egger
2011-05-24 10:29 ` Tim Deegan
2011-05-24 10:33 ` Keir Fraser
2011-05-24 11:46 ` Tim Deegan
2011-05-24 10:31 ` Keir Fraser
2011-05-24 10:47 ` Ian Jackson
2011-05-24 11:38 ` Christoph Egger [this message]
2011-05-24 13:02 ` Ian Jackson
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=4DDB989E.4010609@amd.com \
--to=christoph.egger@amd.com \
--cc=Ian.Campbell@eu.citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--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).