From: Gerd Hoffmann <kraxel@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [FOR 0.12 PATCH 0/4] misc bugfixes
Date: Thu, 10 Dec 2009 13:15:39 +0100 [thread overview]
Message-ID: <4B20E66B.7090509@redhat.com> (raw)
In-Reply-To: <20091210120315.GA13657@redhat.com>
On 12/10/09 13:03, Michael S. Tsirkin wrote:
> On Thu, Dec 10, 2009 at 11:11:04AM +0100, Gerd Hoffmann wrote:
>> Hi,
>>
>> A bunch of fixes for various bugs, mostly hotplug stuff found by Daniel.
>>
>> please apply,
>> Gerd
>>
>
> I am kind of confused by the FOR 0.12 prefix - these
> patches are not on master yet, are they?
No.
> Should patches land on master before being backported
> to 0.12?
Anthony asked to tag patches this way if they should be merged for the
0.12 release. So, after branching, they should go to both master and
0.12 I think. Do we have a 0.12 branch already?
cheers,
Gerd
next prev parent reply other threads:[~2009-12-10 12:15 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-10 10:11 [Qemu-devel] [FOR 0.12 PATCH 0/4] misc bugfixes Gerd Hoffmann
2009-12-10 10:11 ` [Qemu-devel] [FOR 0.12 PATCH 1/4] pci: don't abort() when trying to hotplug with acpi off Gerd Hoffmann
2009-12-10 10:11 ` [Qemu-devel] [FOR 0.12 PATCH 2/4] pci: don't hw_error() when no slot is available Gerd Hoffmann
2009-12-10 12:08 ` [Qemu-devel] " Michael S. Tsirkin
2009-12-10 12:19 ` Gerd Hoffmann
2009-12-10 12:23 ` Michael S. Tsirkin
2009-12-10 13:22 ` Gleb Natapov
2009-12-10 18:04 ` Michael S. Tsirkin
2009-12-10 19:13 ` Gleb Natapov
2009-12-11 10:37 ` Michael S. Tsirkin
2009-12-11 11:03 ` Gleb Natapov
2009-12-10 12:33 ` Alexander Graf
2009-12-10 10:11 ` [Qemu-devel] [FOR 0.12 PATCH 3/4] scsi: fix drive hotplug Gerd Hoffmann
2009-12-10 10:11 ` [Qemu-devel] [FOR 0.12 PATCH 4/4] QemuOpts: allow larger option values Gerd Hoffmann
2009-12-10 12:03 ` [Qemu-devel] Re: [FOR 0.12 PATCH 0/4] misc bugfixes Michael S. Tsirkin
2009-12-10 12:15 ` Gerd Hoffmann [this message]
2009-12-10 15: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=4B20E66B.7090509@redhat.com \
--to=kraxel@redhat.com \
--cc=mst@redhat.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.