From: Stefan Hajnoczi <stefanha@gmail.com>
To: "Justin M. Forbes" <jmforbes@linuxtx.org>
Cc: qemu-devel@nongnu.org, qemu-stable@nongnu.org
Subject: Re: [Qemu-devel] Qemu stable releases
Date: Tue, 6 Dec 2011 09:27:22 +0000 [thread overview]
Message-ID: <CAJSP0QVkyH3VkfxvrEie4bwXiEzxvX=GYioc1VF_pEdPCCfgUQ@mail.gmail.com> (raw)
In-Reply-To: <1323115683.6884.8.camel@fedora64.linuxtx.org>
On Mon, Dec 5, 2011 at 8:08 PM, Justin M. Forbes <jmforbes@linuxtx.org> wrote:
> The stable tree for 1.0 has now been created and the mailing list
> exists.
Where does the stable 1.0 tree live?
Stefan
next prev parent reply other threads:[~2011-12-06 9:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-05 20:08 [Qemu-devel] Qemu stable releases Justin M. Forbes
2011-12-06 9:27 ` Stefan Hajnoczi [this message]
2011-12-09 10:39 ` Richard W.M. Jones
2011-12-09 12:01 ` Richard W.M. Jones
2011-12-09 13:25 ` Anthony Liguori
2011-12-09 13:47 ` Richard W.M. Jones
2011-12-09 12:55 ` Andreas Färber
2011-12-09 13:24 ` Anthony Liguori
2011-12-09 13:50 ` Andreas Färber
2011-12-09 13:28 ` Justin M. Forbes
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='CAJSP0QVkyH3VkfxvrEie4bwXiEzxvX=GYioc1VF_pEdPCCfgUQ@mail.gmail.com' \
--to=stefanha@gmail.com \
--cc=jmforbes@linuxtx.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@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).