From: "Michael S. Tsirkin" <mst@redhat.com>
To: Zhang Haoyu <zhanghy@sangfor.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>, qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [question] Will qemu-2.0.0 be a longterm stable branch?
Date: Tue, 24 Jun 2014 08:49:47 +0300 [thread overview]
Message-ID: <20140624054947.GA25614@redhat.com> (raw)
In-Reply-To: <201406240908546812611@sangfor.com>
On Tue, Jun 24, 2014 at 09:08:56AM +0800, Zhang Haoyu wrote:
> Hi, all
>
> Which version is best for commercial product, qemu-2.0.0 or other versions?
> Any advices?
>
> Thanks,
> Zhang Haoyu
Use one of the downstreams: Red Hat, Fedora, Debian all ship QEMU and
have active QEMU maintainers developing the distribution.
--
MST
next prev parent reply other threads:[~2014-06-24 5:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-24 1:08 [Qemu-devel] [question] Will qemu-2.0.0 be a longterm stable branch? Zhang Haoyu
2014-06-24 5:16 ` Paolo Bonzini
2014-06-24 5:49 ` Michael S. Tsirkin [this message]
2014-06-24 6:45 ` [Qemu-devel] [question] Will qemu-2.0.0 be a longterm stablebranch? Zhang Haoyu
2014-07-02 6:32 ` Michael S. Tsirkin
2014-07-02 9:25 ` Paolo Bonzini
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=20140624054947.GA25614@redhat.com \
--to=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=zhanghy@sangfor.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.