From: Glauber Costa <glommer@redhat.com>
To: qemu-devel@nongnu.org
Cc: markmc@redhat.com, aliguori@us.ibm.com
Subject: [Qemu-devel] qemu-stable git tree
Date: Thu, 21 May 2009 15:42:44 -0300 [thread overview]
Message-ID: <20090521184244.GE24584@poweredge.glommer> (raw)
Hello guys,
I've set up a git tree at:
git://git.kernel.org/pub/scm/virt/qemu/glommer/qemu-stable.git
in which I plan to pick updates for stable. From time to time, Anthony can then
pull from this tree if he sees fit. Right now, this is the very same job he is
already doing, with the difference that you now have an extra person to blame ;)
But in the future, I intend to keep maintaining branches for a while after life
moves on and we release a new version.
That should make packagers life easier, since they can just update to a new
0.x-stable even after 0.(x+1) is out, instead of backporting patches themselves.
I may cherry pick patches at will if I see fit. Every patch I modify during the
backport, even in the smallest way, will be sent to the list, so people can
shout if there is something potentially wrong about it.
reply other threads:[~2009-05-21 18:37 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20090521184244.GE24584@poweredge.glommer \
--to=glommer@redhat.com \
--cc=aliguori@us.ibm.com \
--cc=markmc@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).