From: Jeff Cody <jcody@redhat.com>
To: qemu-block@nongnu.org
Cc: peter.maydell@linaro.org, jcody@redhat.com, qemu-devel@nongnu.org
Subject: [Qemu-devel] [PULL 0/3] Block patches for 2.6
Date: Tue, 19 Apr 2016 12:28:44 -0400 [thread overview]
Message-ID: <1461083327-21993-1-git-send-email-jcody@redhat.com> (raw)
The following changes since commit d4dffa4a3f51b10cc0b7e6e34431919cac7a318e:
Merge remote-tracking branch 'remotes/armbru/tags/pull-fw_cfg-2016-04-19' into staging (2016-04-19 15:25:20 +0100)
are available in the git repository at:
git@github.com:codyprime/qemu-kvm-jtc.git tags/block-pull-request
for you to fetch changes up to d85fa9eb87ba736d2d5ce342fc35f507c8fe29f2:
block/gluster: prevent data loss after i/o error (2016-04-19 12:24:59 -0400)
----------------------------------------------------------------
Gluster patches for 2.6
----------------------------------------------------------------
Jeff Cody (3):
block/gluster: return correct error value
block/gluster: code movement of qemu_gluster_close()
block/gluster: prevent data loss after i/o error
block/gluster.c | 77 +++++++++++++++++++++++++++++++++++++++++++++++----------
configure | 8 ++++++
2 files changed, 72 insertions(+), 13 deletions(-)
--
1.9.3
next reply other threads:[~2016-04-19 16:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-19 16:28 Jeff Cody [this message]
2016-04-19 16:28 ` [Qemu-devel] [PULL 1/3] block/gluster: return correct error value Jeff Cody
2016-04-19 16:28 ` [Qemu-devel] [PULL 2/3] block/gluster: code movement of qemu_gluster_close() Jeff Cody
2016-04-19 16:28 ` [Qemu-devel] [PULL 3/3] block/gluster: prevent data loss after i/o error Jeff Cody
2016-04-20 14:05 ` [Qemu-devel] [PULL 0/3] Block patches for 2.6 Peter Maydell
-- strict thread matches above, loose matches on Subject: below --
2016-03-29 2:49 Jeff Cody
2016-03-29 19:48 ` 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=1461083327-21993-1-git-send-email-jcody@redhat.com \
--to=jcody@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-block@nongnu.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 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.