qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Eric Blake <eblake@redhat.com>
To: "Lluís Vilanova" <vilanova@ac.upc.edu>, qemu-devel@nongnu.org
Cc: "Benoît Canet" <benoit.canet@irqsave.net>,
	"Markus Armbruster" <armbru@redhat.com>,
	"Luiz Capitulino" <lcapitulino@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v10 3/4] qapi: Use an explicit input file
Date: Thu, 01 May 2014 06:37:46 -0600	[thread overview]
Message-ID: <5362401A.1030105@redhat.com> (raw)
In-Reply-To: <20140430190946.7884.46553.stgit@fimbulvetr.bsc.es>

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

On 04/30/2014 01:09 PM, Lluís Vilanova wrote:
> Use an explicit input file on the command-line instead of reading from standard
> input.
> 
> It also outputs the proper file name when there's an error.
> 
> Signed-off-by: Lluís Vilanova <vilanova@ac.upc.edu>
> Reviewed-by: Eric Blake <eblake@redhat.com>

Technically, you made a non-trivial change (use of perl to sanitize
SRC_PATH) in response to a comment that did not come from my review. You
properly called it out in the cover letter, so I looked at this patch
again; but in general, when making non-trivial changes, it's best to
remove the Reviewed-by to make sure that earlier reviewers notice that
they need to look again, and that they are still happy with the changes.

Fortunately, in this case, your changes still look okay, so I'm okay
with leaving my Reviewed-by on this version of the patch.

>  		"  TEST  $*.out")
>  	@diff -q $(SRC_PATH)/$*.out $*.test.out
> -	@diff -q $(SRC_PATH)/$*.err $*.test.err
> +	@# Sanitize error messages (make them independent of build directory)
> +	@perl -p -e 's|\Q$(SRC_PATH)\E/||g' $*.test.err | diff -q $(SRC_PATH)/$*.err -
>  	@diff -q $(SRC_PATH)/$*.exit $*.test.exit
>  

-- 
Eric Blake   eblake redhat com    +1-919-301-3266
Libvirt virtualization library http://libvirt.org


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 604 bytes --]

  parent reply	other threads:[~2014-05-01 12:38 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20140430190928.7884.69380.stgit@fimbulvetr.bsc.es>
     [not found] ` <20140430190934.7884.19499.stgit@fimbulvetr.bsc.es>
2014-05-01 12:34   ` [Qemu-devel] [PATCH v10 1/4] qapi: [trivial] Break long command lines Eric Blake
2014-05-02 12:18     ` Lluís Vilanova
     [not found] ` <20140430190946.7884.46553.stgit@fimbulvetr.bsc.es>
2014-05-01 12:37   ` Eric Blake [this message]
2014-05-02 12:17     ` [Qemu-devel] [PATCH v10 3/4] qapi: Use an explicit input file Lluís Vilanova
     [not found] ` <20140430190951.7884.90848.stgit@fimbulvetr.bsc.es>
2014-05-01 12:47   ` [Qemu-devel] [PATCH v10 4/4] qapi: Add a primitive to include other files from a QAPI schema file Eric Blake
2014-05-02 12:16     ` Lluís Vilanova
2014-05-02 12:23       ` Eric Blake
2014-05-02 13:38         ` Lluís Vilanova
2014-05-02  8:06 ` [Qemu-devel] [PATCH v10 0/4] qapi: Allow modularization of QAPI schema files Markus Armbruster

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=5362401A.1030105@redhat.com \
    --to=eblake@redhat.com \
    --cc=armbru@redhat.com \
    --cc=benoit.canet@irqsave.net \
    --cc=lcapitulino@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=vilanova@ac.upc.edu \
    /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).