From: Gerd Hoffmann <kraxel@redhat.com>
To: seabios@seabios.org
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [SeaBIOS] qemu 1.7 & seabios -- release planning
Date: Tue, 29 Oct 2013 10:15:58 +0100 [thread overview]
Message-ID: <1383038158.7970.10.camel@nilsson.home.kraxel.org> (raw)
In-Reply-To: <1381831445.3709.58.camel@nilsson.home.kraxel.org>
On Di, 2013-10-15 at 12:04 +0200, Gerd Hoffmann wrote:
> Hi,
>
> It's probably going to be a bit tough this time. We are pretty late in
> the qemu 1.7 devel cycle, soft freeze today, and a big chunk of code
> (ahci-tables-from qemu) which needs seabios support[1] is just about to
> be pulled.
Update: ahci-tables-from was NOT pulled to 1.7 and will likely be merged
in the 1.8 devel cycle, hopefully early. I think we should plan for a
release soon after the patches got merged, but there is no need to rush
it, qemu 1.7 will do fine with the latest stable release currently in
the tree.
cheers,
Gerd
prev parent reply other threads:[~2013-10-29 9:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-15 10:04 [Qemu-devel] qemu 1.7 & seabios -- release planning Gerd Hoffmann
2013-10-15 12:40 ` [Qemu-devel] [SeaBIOS] " Kevin O'Connor
2013-10-29 9:15 ` Gerd Hoffmann [this message]
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=1383038158.7970.10.camel@nilsson.home.kraxel.org \
--to=kraxel@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=seabios@seabios.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).