From: Jes Sorensen <Jes.Sorensen@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: Chris Wright <chrisw@redhat.com>,
kvm@vger.kernel.org, qemu-devel@nongnu.org,
Jan Kiszka <jan.kiszka@web.de>, Avi Kivity <avi@redhat.com>
Subject: Re: [Qemu-devel] Re: KVM call agenda for Mar 23
Date: Tue, 23 Mar 2010 13:56:36 +0100 [thread overview]
Message-ID: <4BA8BA84.3020908@redhat.com> (raw)
In-Reply-To: <4BA8B7FB.2050103@codemonkey.ws>
On 03/23/10 13:45, Anthony Liguori wrote:
> I don't think we can pull in:
>
> - extboot
> - ia64
> - in-kernel pit[1]
> - associated command line options
> - device passthrough
>
> The question is, if we dropped those things, would people actually use
> qemu.git instead of qemu-kvm.git. If the answer is "no", what set of
> things do we need in order for people to focus on qemu.git instead of
> qemu-kvm.git.
I am not sure if anyone is still actively working on ia64. According to
the qemu-kvm.git logs, there hasn't been any real ia64 changes to the
code since my last commit in June of last year and then a couple of
minor configure bits.
IMHO we can just let it rot - not sure if Xiantao is still interested?
Cheers,
Jes
next prev parent reply other threads:[~2010-03-23 12:56 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-23 6:11 [Qemu-devel] KVM call agenda for Mar 23 Chris Wright
2010-03-23 8:40 ` [Qemu-devel] " Juan Quintela
2010-03-23 13:25 ` Juan Quintela
2010-03-23 9:31 ` Jan Kiszka
2010-03-23 9:52 ` Avi Kivity
2010-03-23 10:50 ` Jan Kiszka
2010-03-23 10:57 ` Avi Kivity
2010-03-23 11:13 ` Jan Kiszka
2010-03-23 12:29 ` Avi Kivity
2010-03-23 12:45 ` Anthony Liguori
2010-03-23 12:51 ` Avi Kivity
2010-03-23 12:56 ` Jes Sorensen [this message]
2010-03-25 1:31 ` Zhang, Xiantao
2010-03-25 9:39 ` Jan Kiszka
2010-03-25 9:43 ` Jes Sorensen
2010-03-26 18:48 ` Chris Wright
2010-03-23 12:40 ` Anthony Liguori
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=4BA8BA84.3020908@redhat.com \
--to=jes.sorensen@redhat.com \
--cc=anthony@codemonkey.ws \
--cc=avi@redhat.com \
--cc=chrisw@redhat.com \
--cc=jan.kiszka@web.de \
--cc=kvm@vger.kernel.org \
--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).