qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Weil <weil@mail.berlios.de>
To: Anthony Liguori <aliguori@linux.vnet.ibm.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
	Marcelo Tosatti <mtosatti@redhat.com>,
	Juan Quintela <quintela@redhat.com>,
	"Michael S. Tsirkin" <mst@redhat.com>,
	qemu-devel <qemu-devel@nongnu.org>,
	Luiz Capitulino <lcapitulino@redhat.com>,
	Blue Swirl <blauwirbel@gmail.com>,
	Aurelien Jarno <aurelien@aurel32.net>
Subject: Re: [Qemu-devel] [RFT] qemu 0.13.0-rc3
Date: Tue, 12 Oct 2010 18:27:15 +0200	[thread overview]
Message-ID: <4CB48C63.2010202@mail.berlios.de> (raw)
In-Reply-To: <4CB38C82.1090403@linux.vnet.ibm.com>

Am 12.10.2010 00:15, schrieb Anthony Liguori:
> After suffering from a prolonged maintainer softlockup, I'm attempting 
> to get 0.13.0 release process back on track.
>
> I've tagged qemu-0.13.0-rc3 in git which only carries a few changes 
> since 0.13.0-rc1.  Most notably, a series of updates from Kevin Wolf 
> and Cam Macdonell's ivshmem device.
>
> I think we're pretty good testing wise for the final release but I 
> wanted to offer a 24-hour window for last minute fixes.  I'm only 
> interested in the following:
>
> 1) Patches that are *tested* against the stable-0.13 branch that are 
> already committed in master.  Please tell me explicitly that you've 
> tested the patch and how you've tested it.
>
> 2) Pull requests from other maintainers with cherry-picked patches 
> against stable-0.13 that have been tested.
>
> If you don't already have something ready, it's probably not worth 
> worrying about.  We can follow with 0.13.1 in a relatively short 
> period of time.
>
> So please get any requests to me before 6PM US Central time October 12th.
>
> Post 0.13.0, as part of the 0.14 planning, we can discuss how to avoid 
> future delay with releases.
>
> Thanks!
>
> Regards,
>
> Anthony Liguori
>
>

Michael's last PCI pull request ([PULL] eeepro100, virtio, net, vhost fixes)
was proposed for master and for 0.13, too.

I tested the patch 010ec6293409f10b88631c36145944b9c3277ce1
"eepro100: Add support for multiple individual addresses (multiple IA))"
and suggest to include it.

Regards,
Stefan Weil

  parent reply	other threads:[~2010-10-12 16:27 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-11 22:15 [Qemu-devel] [RFT] qemu 0.13.0-rc3 Anthony Liguori
2010-10-11 23:45 ` [Qemu-devel] " Luiz Capitulino
2010-10-12  0:02   ` Anthony Liguori
2010-10-12 15:43 ` [Qemu-devel] " Rick Vernam
2010-10-12 16:27 ` Stefan Weil [this message]
2010-10-12 21:34 ` Juergen Lock
2010-10-12 22:00   ` Anthony Liguori
2010-10-13  3:28     ` Juergen Lock
2010-10-13 19:12       ` [Qemu-devel] [PATCH] (master, stable-0.13) zaurus: workaround for io base address rounded down Juergen Lock
2010-10-13 19:45         ` Blue Swirl
2010-10-13 21:30           ` Juergen Lock
2010-10-13 19:24       ` [Qemu-devel] [RFT] qemu 0.13.0-rc3 Juergen Lock
2010-10-13  9:41 ` Amit Shah

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=4CB48C63.2010202@mail.berlios.de \
    --to=weil@mail.berlios.de \
    --cc=aliguori@linux.vnet.ibm.com \
    --cc=aurelien@aurel32.net \
    --cc=blauwirbel@gmail.com \
    --cc=kwolf@redhat.com \
    --cc=lcapitulino@redhat.com \
    --cc=mst@redhat.com \
    --cc=mtosatti@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=quintela@redhat.com \
    /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).