From: Anthony Liguori <aliguori@linux.vnet.ibm.com>
To: qemu-devel <qemu-devel@nongnu.org>
Cc: "Justin M. Forbes" <jmforbes@linuxtx.org>
Subject: [Qemu-devel] New stable branch information
Date: Fri, 04 Feb 2011 06:25:26 -0600 [thread overview]
Message-ID: <4D4BF036.3050005@linux.vnet.ibm.com> (raw)
To help make the stable branch more active than it has been in the past,
I'd like to split the stable branch into a separate tree to allow the
tree to develop a life of its own over time.
I'd like to begin this process with 0.14 and as such, have created a new
stable tree at git://git.qemu.org/qemu-stable-0.14.git.
Justin Forbes has volunteered to help collect patches for this tree.
The same stable rules still apply: patches should go into master first
except for rare exceptions where that's feasible.
I plan on making the stable-0.14 branch in git be a mirror of the
stable-0.14.git tree so it shouldn't really affect most people.
However, I probably won't set this up until after next week.
Regards,
Anthony Liguori
next reply other threads:[~2011-02-04 12:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-04 12:25 Anthony Liguori [this message]
2011-02-04 19:26 ` [Qemu-devel] New stable branch information Aurelien Jarno
2011-02-04 20:48 ` Justin M. Forbes
2011-02-05 9:11 ` Michael Tokarev
2011-02-07 13:07 ` Anthony Liguori
2011-02-07 14:09 ` Markus Armbruster
2011-02-07 14:32 ` 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=4D4BF036.3050005@linux.vnet.ibm.com \
--to=aliguori@linux.vnet.ibm.com \
--cc=jmforbes@linuxtx.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).