From: Eric Blake <eblake@redhat.com>
To: li.shanlue@zte.com.cn, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] wurb test zt
Date: Fri, 20 Oct 2017 09:50:24 -0500 [thread overview]
Message-ID: <7bb7ca98-1c17-7815-7f58-228c04f93ba9@redhat.com> (raw)
In-Reply-To: <201710201734276973012@zte.com.cn>
[-- Attachment #1: Type: text/plain, Size: 450 bytes --]
On 10/20/2017 04:34 AM, li.shanlue@zte.com.cn wrote:
> reply for an original mail from mail group system
Rather than spamming all list readers with test mails with no relevance,
can you include topics relevant to qemu as part of your test? Also,
technical lists don't mesh well with your style of top-posting.
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3266
Virtualization: qemu.org | libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 619 bytes --]
next prev parent reply other threads:[~2017-10-20 14:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-20 9:34 [Qemu-devel] wurb test zt li.shanlue
2017-10-20 14:50 ` Eric Blake [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-10-20 9:30 li.shanlue
2017-10-21 5:02 ` wan.manlan
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=7bb7ca98-1c17-7815-7f58-228c04f93ba9@redhat.com \
--to=eblake@redhat.com \
--cc=li.shanlue@zte.com.cn \
--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).