From: "Daniel P. Berrange" <berrange@redhat.com>
To: "sochin.jiang" <sochin.jiang@huawei.com>
Cc: qemu-devel@nongnu.org, eric.fangyi@huawei.com
Subject: Re: [Qemu-devel] [PATCH] scripts: correct a spelling error
Date: Wed, 20 Dec 2017 10:31:31 +0000 [thread overview]
Message-ID: <20171220103131.GN21216@redhat.com> (raw)
In-Reply-To: <1513764401-24239-1-git-send-email-sochin.jiang@huawei.com>
On Wed, Dec 20, 2017 at 06:06:41PM +0800, sochin.jiang wrote:
> From: "sochin.jiang" <sochin.jiang@huawei.com>
>
> Correct a spelling error in prompt message.
>
> Signed-off-by: sochin.jiang <sochin.jiang@huawei.com>
This fix is already sent 3 times now & on the qemu-trivial queue....
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
prev parent reply other threads:[~2017-12-20 10:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-20 10:06 [Qemu-devel] [PATCH] scripts: correct a spelling error sochin.jiang
2017-12-20 10:31 ` Daniel P. Berrange [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=20171220103131.GN21216@redhat.com \
--to=berrange@redhat.com \
--cc=eric.fangyi@huawei.com \
--cc=qemu-devel@nongnu.org \
--cc=sochin.jiang@huawei.com \
/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).