All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: qemu-devel@nongnu.org
Cc: Avi Kivity <avi@redhat.com>
Subject: Re: [Qemu-devel] ANNOUNCE: Release 0.10.0 of QEMU
Date: Wed, 04 Mar 2009 20:29:57 -0600	[thread overview]
Message-ID: <49AF3925.4050506@codemonkey.ws> (raw)
In-Reply-To: <bfdeacfa0903041635t45221305k6666518a77c34ade@mail.gmail.com>

Mark Bidewell wrote:
> Does this new release change the way in which the KVM and Qemu
> projects interact or will KVM continue to maintain its own updated
> Qemu version?
>   

You can think of KVM's QEMU tree as a staging tree.  There are some 
large changes that are taking some time to merge fully, but we're slowly 
getting there.  A huge chunk of the changes in KVM's tree have already 
been merged for this release.  At the current rate, we should have 
almost everything merged by the next QEMU release.

I don't want to speak for Avi, but I expect that we'll start seeing KVM 
userspace releases that more closely match the QEMU release process too.

Regards,

Anthony Liguori

  reply	other threads:[~2009-03-05  2:30 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-04 23:01 [Qemu-devel] ANNOUNCE: Release 0.10.0 of QEMU Anthony Liguori
2009-03-05  0:35 ` Mark Bidewell
2009-03-05  2:29   ` Anthony Liguori [this message]
2009-03-05  1:49 ` Natalia Portillo
2009-03-05  2:00 ` Jonathan Kalbfeld
2009-03-05  3:54 ` Jonathan Kalbfeld
2009-03-05  9:48 ` Lubomir Rintel
2009-03-05 18:44   ` Anthony Liguori
2009-03-06  1:08     ` Jamie Lokier
2009-03-05 16:40 ` Jean-Christophe PLAGNIOL-VILLARD
2009-03-05 18:47 ` Anthony Liguori
2009-03-05 19:23   ` Geraldo Netto
2009-03-07  0:44     ` Rob Landley
2009-03-07  9:53       ` Andreas Färber
2009-03-08 16:33     ` Stuart Brady
2009-03-08 18:33       ` Anthony Liguori
2009-03-06  4:13 ` Mulyadi Santosa

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=49AF3925.4050506@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --cc=avi@redhat.com \
    --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 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.