From: Kevin Wolf <kwolf@redhat.com>
To: bharata@linux.vnet.ibm.com
Cc: Paolo Bonzini <pbonzini@redhat.com>,
Anthony Liguori <aliguori@us.ibm.com>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v1] qemu: Document GlusterFS block driver usage
Date: Wed, 24 Oct 2012 15:05:07 +0200 [thread overview]
Message-ID: <5087E783.4060304@redhat.com> (raw)
In-Reply-To: <20121024114753.GG16487@in.ibm.com>
Am 24.10.2012 13:47, schrieb Bharata B Rao:
> qemu: Document GlusterFS block driver usage
>
> From: Bharata B Rao <bharata@linux.vnet.ibm.com>
Please don't repeat the subject line and From: header in the body.
>
> Signed-off-by: Bharata B Rao <bharata@linux.vnet.ibm.com>
> ---
> qemu-doc.texi | 49 +++++++++++++++++++++++++++++++++++++++++++++++++
> qemu-options.hx | 17 +++++++++++++++++
> 2 files changed, 66 insertions(+)
Thanks, fixed the commit message and applied to the block branch.
Kevin
prev parent reply other threads:[~2012-10-24 13:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-24 11:47 [Qemu-devel] [PATCH v1] qemu: Document GlusterFS block driver usage Bharata B Rao
2012-10-24 13:05 ` Kevin Wolf [this message]
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=5087E783.4060304@redhat.com \
--to=kwolf@redhat.com \
--cc=aliguori@us.ibm.com \
--cc=bharata@linux.vnet.ibm.com \
--cc=pbonzini@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 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).