From: "Zhang Haoyu" <zhanghy@sangfor.com>
To: "Michael S. Tsirkin" <mst@redhat.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 stablebranch?
Date: Tue, 24 Jun 2014 14:45:44 +0800 [thread overview]
Message-ID: <201406241445428077130@sangfor.com> (raw)
In-Reply-To: 20140624054947.GA25614@redhat.com
>> 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.
>
How to get the latest qemu distribution shipped by RedHat?
Thanks,
Zhang Haoyu
>--
>MST
next prev parent reply other threads:[~2014-06-24 6:46 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
2014-06-24 6:45 ` Zhang Haoyu [this message]
2014-07-02 6:32 ` [Qemu-devel] [question] Will qemu-2.0.0 be a longterm stablebranch? 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=201406241445428077130@sangfor.com \
--to=zhanghy@sangfor.com \
--cc=mst@redhat.com \
--cc=pbonzini@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 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).