From: Rick Vernam <rickv@hobi.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [RFT] qemu 0.13.0-rc3
Date: Tue, 12 Oct 2010 10:43:20 -0500 [thread overview]
Message-ID: <201010121043.20627.rickv@hobi.com> (raw)
In-Reply-To: <4CB38C82.1090403@linux.vnet.ibm.com>
I encountered two issues with 0.13.0-rc1, not sure how to tell if the patches
have been applied?
one is this patch: http://patchwork.ozlabs.org/patch/62420/
discussed here:
http://lists.nongnu.org/archive/html/qemu-devel/2010-09/msg01114.html
the other was
http://lists.nongnu.org/archive/html/qemu-devel/2010-09/msg01165.html
which was applied to seabios, but how can I determine if the shipped seabios
includes this particular patch?
Sorry for the noise...
On Monday 11 October 2010 17:15:30 Anthony Liguori wrote:
> 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
next prev parent reply other threads:[~2010-10-12 15:43 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 ` Rick Vernam [this message]
2010-10-12 16:27 ` [Qemu-devel] " Stefan Weil
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=201010121043.20627.rickv@hobi.com \
--to=rickv@hobi.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.