qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Eric Blake <eblake@redhat.com>
To: Stefan Hajnoczi <stefanha@redhat.com>, qemu-devel@nongnu.org
Cc: "Kevin Wolf" <kwolf@redhat.com>, "John Snow" <jsnow@redhat.com>,
	"Philippe Mathieu-Daudé" <f4bug@amsat.org>,
	"Peter Maydell" <peter.maydell@linaro.org>,
	qemu-block@nongnu.org, "Jeff Cody" <jcody@redhat.com>,
	"Ishani Chugh" <chugh.ishani@research.iiit.ac.in>
Subject: Re: [Qemu-devel] [PATCH v3] qemu-iotests: add a "how to" to ./README
Date: Mon, 31 Jul 2017 12:28:44 -0500	[thread overview]
Message-ID: <fbe60111-cd7b-a69f-fc69-a385cd192b3c@redhat.com> (raw)
In-Reply-To: <20170731162641.24160-1-stefanha@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 802 bytes --]

On 07/31/2017 11:26 AM, Stefan Hajnoczi wrote:
> There is not much getting started documentation for qemu-iotests.  This
> patch explains how to create a new test and covers the overall testing
> approach.
> 
> Cc: Ishani Chugh <chugh.ishani@research.iiit.ac.in>
> Reviewed-by: Eric Blake <eblake@redhat.com>
> Reviewed-by: Philippe Mathieu-Daudé <f4bug@amsat.org>
> Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
> ---

>  Please send improvements to the test suite, general feedback or just
>  reports of failing tests cases to qemu-devel@nongnu.org with a CC:
>  to qemu-block@nongnu.org.
> +
> 

Is this adding a spurious blank line at EOF?

-- 
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 --]

  parent reply	other threads:[~2017-07-31 17:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-31 16:26 [Qemu-devel] [PATCH v3] qemu-iotests: add a "how to" to ./README Stefan Hajnoczi
2017-07-31 17:14 ` Jeff Cody
2017-07-31 17:28 ` Eric Blake [this message]
2017-08-01  9:22   ` [Qemu-devel] [Qemu-block] " Stefan Hajnoczi
2017-07-31 19:02 ` [Qemu-devel] " John Snow

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=fbe60111-cd7b-a69f-fc69-a385cd192b3c@redhat.com \
    --to=eblake@redhat.com \
    --cc=chugh.ishani@research.iiit.ac.in \
    --cc=f4bug@amsat.org \
    --cc=jcody@redhat.com \
    --cc=jsnow@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.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).