From: Gerd Hoffmann <kraxel@redhat.com>
To: qemu-devel@nongnu.org, seabios@seabios.org
Cc: Gerd Hoffmann <kraxel@redhat.com>
Subject: [Qemu-devel] [PULL 0/1] update qemu seabios / seabios release?
Date: Tue, 7 Aug 2012 17:45:07 +0200 [thread overview]
Message-ID: <1344354308-10994-1-git-send-email-kraxel@redhat.com> (raw)
Hi,
This pull updates seabios in qemu to the latest bits from seabios
master, so the upcoming 1.2 qemu release gets all the new shiny
stuff added recently. I'd like to have a new seabios release for
inclusion into qemu 1.2 which is planned for September 1st.
So how about this plan:
- merge seabios snapshot now (this pull req), so it gets testing
in the qemu testing & release candidates phase
- put seabios into bugfixing freeze too (now or in a few days),
fix any issues poping up in testing.
- roll out seabios release by end of august, so it can be included
into qemu 1.2
Anthony? Kevin? Fine are you ok with this?
qemu release schedule is here: http://wiki.qemu.org/Planning/1.2
cheers,
Gerd
Gerd Hoffmann (1):
update seabios to latest master
pc-bios/bios.bin | Bin 131072 -> 131072 bytes
roms/seabios | 2 +-
2 files changed, 1 insertions(+), 1 deletions(-)
The following changes since commit 0b8db8fe15d17a529a5ea90614c11e9f031dfee8:
slirp: fix build on mingw32 (2012-08-06 19:31:55 -0500)
are available in the git repository at:
git://git.kraxel.org/qemu seabios-5a02306
Gerd Hoffmann (1):
update seabios to latest master
pc-bios/bios.bin | Bin 131072 -> 131072 bytes
roms/seabios | 2 +-
2 files changed, 1 insertions(+), 1 deletions(-)
next reply other threads:[~2012-08-07 15:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-07 15:45 Gerd Hoffmann [this message]
2012-08-07 15:45 ` [Qemu-devel] [PATCH 1/1] update seabios to latest master Gerd Hoffmann
2012-08-09 11:57 ` [Qemu-devel] [PULL 0/1] update qemu seabios / seabios release? Kevin O'Connor
2012-08-09 12:57 ` Gerd Hoffmann
2012-08-10 13:42 ` [Qemu-devel] [SeaBIOS] " Anthony Liguori
2012-08-14 0:55 ` Kevin O'Connor
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=1344354308-10994-1-git-send-email-kraxel@redhat.com \
--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).