From: Anthony Liguori <anthony@codemonkey.ws>
To: qemu-devel <qemu-devel@nongnu.org>,
seabios@seabios.org, Kevin O'Connor <kevin@koconnor.net>
Subject: [Qemu-devel] Advise on updating SeaBIOS in stable
Date: Tue, 12 Jan 2010 13:43:47 -0600 [thread overview]
Message-ID: <4B4CD0F3.2050607@codemonkey.ws> (raw)
Hi,
I'm ready to cut another qemu stable release and I'm contemplating
whether to update to 0.5.1 in stable. Generally speaking, we try to
limit stable to bug fixes and changes that aren't user visible.
0.5.1 looks like a point on the master branch as opposed to a separate
branch. I wonder what the thinking is within SeaBIOS about what sort of
changes will be in the 0.5.x series vs. what would result in 0.6.0.
Regards,
Anthony Liguori
next reply other threads:[~2010-01-12 19:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-12 19:43 Anthony Liguori [this message]
2010-01-13 4:51 ` [Qemu-devel] Re: Advise on updating SeaBIOS in stable Kevin O'Connor
2010-01-13 23:58 ` Anthony Liguori
2010-01-14 6:11 ` Aurelien Jarno
2010-01-14 10:27 ` [Qemu-devel] Re: [SeaBIOS] " Gerd Hoffmann
2010-01-14 13:46 ` [Qemu-devel] " Kevin O'Connor
2010-01-14 14:37 ` 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=4B4CD0F3.2050607@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=kevin@koconnor.net \
--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).