From: "Andreas Färber" <afaerber@suse.de>
To: qemu-devel <qemu-devel@nongnu.org>, Stefan Hajnoczi <stefanha@gmail.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
Juan Quintela <quintela@redhat.com>,
Michael Roth <mdroth@linux.vnet.ibm.com>,
Anthony Liguori <anthony@codemonkey.ws>,
Igor Mammedov <imammedo@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] Plans for the hard feature freeze
Date: Fri, 11 May 2012 03:49:44 +0200 [thread overview]
Message-ID: <4FAC7038.1080800@suse.de> (raw)
In-Reply-To: <4F9D8F2F.3090507@codemonkey.ws>
Am 29.04.2012 20:57, schrieb Anthony Liguori:
> We'll run this release much like the last one. All bug fixing will
> happen in master until 1.1 is released. If you plan on maintaining a
> subsystem tree while we're in feature freeze, please respond to this
> note with information about your tree.
On Paolo's suggestion and with Anthony's blessing I have set up a
qom-next tree:
T: git git://repo.or.cz/qemu/afaerber.git qom-next
T: git http://repo.or.cz/r/qemu/afaerber.git qom-next
W: http://repo.or.cz/w/qemu/afaerber.git/shortlog/refs/heads/qom-next
This is intended as temporary solution to minimize conflicts between QOM
refactorings or features during the Hard Freeze and to facilitate a
quick and painless merge into master once the window for 1.2 opens.
Stefan, can you add this branch to the build bots please?
qom-next will track master as a patch queue, rebasing as necessary.
So if you want to add a tag or find a patch is bogus, say so. :)
Regards,
Andreas
--
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
next parent reply other threads:[~2012-05-11 1:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4F9D8F2F.3090507@codemonkey.ws>
2012-05-11 1:49 ` Andreas Färber [this message]
2012-05-11 2:00 ` [Qemu-devel] Plans for the hard feature freeze Anthony Liguori
2012-06-21 13:23 ` Andreas Färber
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=4FAC7038.1080800@suse.de \
--to=afaerber@suse.de \
--cc=anthony@codemonkey.ws \
--cc=imammedo@redhat.com \
--cc=mdroth@linux.vnet.ibm.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=stefanha@gmail.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.