qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Gerd Hoffmann <kraxel@redhat.com>
To: Kevin O'Connor <kevin@koconnor.net>
Cc: seabios <seabios@seabios.org>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [SeaBIOS] Time for a seabios 1.11 release?
Date: Thu, 28 Sep 2017 10:08:03 +0200	[thread overview]
Message-ID: <1506586083.6902.1.camel@redhat.com> (raw)
In-Reply-To: <20170927135119.GA15789@morn.lan>

On Wed, 2017-09-27 at 09:51 -0400, Kevin O'Connor wrote:
> On Tue, Sep 26, 2017 at 09:33:09AM +0200, Gerd Hoffmann wrote:
> >    Hi,
> > 
> > Quite a few changes accumulated in master.  Time to plan a new
> > release
> > I think, so we can pick up the improvements in qemu 2.11.
> > 
> > Comments?
> 
> Makes sense.  How about freezing SeaBIOS on October 13th and target a
> release on October 27th?

Looks good to me.

cheers,
  Gerd

  reply	other threads:[~2017-09-28  8:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-26  7:33 [Qemu-devel] Time for a seabios 1.11 release? Gerd Hoffmann
2017-09-27 13:51 ` [Qemu-devel] [SeaBIOS] " Kevin O'Connor
2017-09-28  8:08   ` Gerd Hoffmann [this message]
2017-10-27 23:13     ` 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=1506586083.6902.1.camel@redhat.com \
    --to=kraxel@redhat.com \
    --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).