From: Kevin Wolf <kwolf@redhat.com>
To: Brian Jackson <iggy@theiggy.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PULL 0/5] Block patches
Date: Tue, 13 Jul 2010 18:47:37 +0200 [thread overview]
Message-ID: <4C3C98A9.8010705@redhat.com> (raw)
In-Reply-To: <201007131143.06978.iggy@theiggy.com>
Am 13.07.2010 18:43, schrieb Brian Jackson:
> On Tuesday, July 13, 2010 10:54:21 am Kevin Wolf wrote:
>> These are some more fixes that should go into 0.13.
>
>
> Any of these 0.12-stable material?
I'll try to have a closer look tomorrow. Probably not these, but I think
there are some more patches in git master which could go into 0.12-stable.
Kevin
next prev parent reply other threads:[~2010-07-13 16:47 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-13 15:54 [Qemu-devel] [PULL 0/5] Block patches Kevin Wolf
2010-07-13 15:54 ` [Qemu-devel] [PATCH 1/5] qemu-img: Fix copy+paste bug in documentation Kevin Wolf
2010-07-13 15:54 ` [Qemu-devel] [PATCH 2/5] Block migration fail, ignore error from bdrv_getlength Kevin Wolf
2010-07-13 15:54 ` [Qemu-devel] [PATCH 3/5] virtio-pci: Check for virtio_blk_init() failure Kevin Wolf
2010-07-13 15:54 ` [Qemu-devel] [PATCH 4/5] virtio-blk: Fix virtio-blk-s390 to require drive Kevin Wolf
2010-07-13 15:54 ` [Qemu-devel] [PATCH 5/5] ide scsi virtio-blk: Reject empty drives unless media is removable Kevin Wolf
2010-07-13 16:43 ` [Qemu-devel] [PULL 0/5] Block patches Brian Jackson
2010-07-13 16:47 ` Kevin Wolf [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-10-09 9:13 Stefan Hajnoczi
2015-10-09 11:17 ` Peter Maydell
2015-10-12 8:27 ` Stefan Hajnoczi
2017-02-01 5:34 Jeff Cody
2017-02-02 15:14 ` Peter Maydell
2017-10-03 19:12 Stefan Hajnoczi
2017-10-05 12:27 ` Peter Maydell
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=4C3C98A9.8010705@redhat.com \
--to=kwolf@redhat.com \
--cc=iggy@theiggy.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 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).