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/2] Block patches
Date: Tue, 13 Sep 2016 01:42:11 -0400 [thread overview]
Message-ID: <1473745333-7548-1-git-send-email-jcody@redhat.com> (raw)
The following changes since commit 7263da78045dc91cc207f350911efe4259e99b3c:
Merge remote-tracking branch 'remotes/mcayland/tags/qemu-openbios-signed' into staging (2016-09-12 15:09:47 +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 c76d7aab81c264e3452e778f030fb3760e5edbb9:
qapi/block-core: add doc describing GlusterServer vs. SocketAddress (2016-09-13 01:34:55 -0400)
----------------------------------------------------------------
Block patches
----------------------------------------------------------------
Prasanna Kumar Kalever (2):
block/gluster: add support to choose libgfapi logfile
qapi/block-core: add doc describing GlusterServer vs. SocketAddress
block/gluster.c | 42 ++++++++++++++++++++++++++++++++++++++----
qapi/block-core.json | 17 ++++++++++++++++-
2 files changed, 54 insertions(+), 5 deletions(-)
--
2.7.4
next reply other threads:[~2016-09-13 5:42 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-13 5:42 Jeff Cody [this message]
2016-09-13 5:42 ` [Qemu-devel] [PULL 1/2] block/gluster: add support to choose libgfapi logfile Jeff Cody
2016-09-13 15:23 ` Eric Blake
2016-09-13 15:25 ` Jeff Cody
2016-09-13 5:42 ` [Qemu-devel] [PULL 2/2] qapi/block-core: add doc describing GlusterServer vs. SocketAddress Jeff Cody
2016-09-13 11:59 ` [Qemu-devel] [PULL 0/2] Block patches Peter Maydell
-- strict thread matches above, loose matches on Subject: below --
2019-08-22 15:53 Stefan Hajnoczi
2019-08-27 9:00 ` Peter Maydell
2019-01-14 16:34 Stefan Hajnoczi
2019-01-15 18:07 ` Peter Maydell
2018-12-12 9:52 Stefan Hajnoczi
2018-12-13 13:05 ` Peter Maydell
2018-10-29 13:56 Stefan Hajnoczi
2018-10-29 18:23 ` Peter Maydell
2018-10-12 1:50 Fam Zheng
2018-10-12 11:39 ` Peter Maydell
2018-08-22 3:43 Jeff Cody
2018-08-23 18:02 ` Peter Maydell
2018-06-27 14:48 Stefan Hajnoczi
2018-06-28 16:43 ` Peter Maydell
2018-07-01 14:58 ` no-reply
2018-07-02 6:19 ` Fam Zheng
2018-06-05 14:19 Jeff Cody
2018-06-05 15:11 ` Peter Maydell
2018-02-01 4:06 Jeff Cody
2018-02-02 10:57 ` Peter Maydell
2018-01-22 12:40 Stefan Hajnoczi
2018-01-22 13:54 ` Stefan Hajnoczi
2017-07-18 4:17 Jeff Cody
2017-07-18 20:13 ` Peter Maydell
2017-07-17 15:40 Stefan Hajnoczi
2017-07-18 13:13 ` Peter Maydell
2017-06-30 14:10 Fam Zheng
2017-06-30 16:55 ` Peter Maydell
2017-06-28 12:20 Stefan Hajnoczi
2017-06-28 12:48 ` Stefan Hajnoczi
2017-06-14 21:55 Jeff Cody
2017-06-14 22:26 ` no-reply
2017-06-15 4:30 ` Jeff Cody
2017-06-15 7:28 ` Juan Quintela
2017-06-20 10:13 ` Peter Maydell
2017-02-28 4:37 Jeff Cody
2017-02-28 14:49 ` Peter Maydell
2016-03-17 11:08 Stefan Hajnoczi
2016-03-17 12:43 ` Peter Maydell
2015-09-02 16:01 Stefan Hajnoczi
2015-09-03 10:14 ` Peter Maydell
2015-08-14 14:41 Stefan Hajnoczi
2015-08-14 15:52 ` Peter Maydell
2015-03-12 19:10 Stefan Hajnoczi
2015-03-13 11:00 ` Peter Maydell
2013-03-25 11:00 Stefan Hajnoczi
2013-03-25 11:54 ` Richard W.M. Jones
2013-03-25 12:15 ` Eric Blake
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=1473745333-7548-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.