qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Samuel Thibault <samuel.thibault@gnu.org>
To: QEMU Developer <qemu-devel@nongnu.org>, peter.maydell@linaro.org
Subject: Re: [Qemu-devel] last call for bugs that need to be fixed for 2.6 release!
Date: Thu, 28 Apr 2016 15:22:17 +0200	[thread overview]
Message-ID: <20160428132217.GM3153@var.bordeaux.inria.fr> (raw)
In-Reply-To: <20160418125135.GD2801@var.bordeaux.inria.fr>

Hello,

Peter wrote:
> Hi; looking at http://wiki.qemu.org/Planning/2.6#Known_issues and
> the mailing list we seem to be in reasonable shape for the 2.6 release.
> I would ideally like the 2.6rc3 tarball which we will make later this
> week to be the final one before full release.
> 
> This is therefore the last call for any bugs that need to be fixed
> for 2.6 or patches that must go in. If you have anything you think
> should go into 2.6 please either add it to the "still unfixed in
> master" part of the planning wiki page or follow up to this email to
> describe it/link to the relevant patches/etc.

We very probably want to fix slirp on Darwin, see thread starting at

http://lists.nongnu.org/archive/html/qemu-devel/2016-04/msg03868.html

and patch submitted for review on 

http://lists.nongnu.org/archive/html/qemu-devel/2016-04/msg04262.html

Samuel

  reply	other threads:[~2016-04-28 13:22 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-18 11:22 [Qemu-devel] last call for bugs that need to be fixed for 2.6 release! Peter Maydell
2016-04-18 12:23 ` Mark Cave-Ayland
2016-04-18 13:58   ` David Gibson
2016-04-18 12:51 ` Samuel Thibault
2016-04-28 13:22   ` Samuel Thibault [this message]
2016-04-18 13:02 ` Peter Maydell
2016-04-18 13:44   ` Stefan Weil
2016-04-18 13:52     ` Peter Maydell
2016-04-19  9:10 ` Kevin Wolf
2016-04-19 10:49   ` Jeff Cody
2016-04-20 12:21 ` Kevin Wolf
2016-04-27 15:44 ` Markus Armbruster
2016-04-28 13:30 ` Kevin Wolf

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=20160428132217.GM3153@var.bordeaux.inria.fr \
    --to=samuel.thibault@gnu.org \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.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).