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 1/4] qapi: [trivial] Break long command lines
Date: Thu, 01 May 2014 06:34:24 -0600	[thread overview]
Message-ID: <53623F50.2000802@redhat.com> (raw)
In-Reply-To: <20140430190934.7884.19499.stgit@fimbulvetr.bsc.es>

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

On 04/30/2014 01:09 PM, Lluís Vilanova wrote:
> Signed-off-by: Lluís Vilanova <vilanova@ac.upc.edu>
> Reviewed-by: Eric Blake <eblake@redhat.com>
> ---
>  Makefile       |   24 ++++++++++++++++++------
>  tests/Makefile |   20 ++++++++++++++++----
>  2 files changed, 34 insertions(+), 10 deletions(-)
> 

> @@ -362,7 +368,13 @@ check-tests/test-qapi.py: tests/test-qapi.py
>  
>  .PHONY: $(patsubst %, check-%, $(check-qapi-schema-y))
>  $(patsubst %, check-%, $(check-qapi-schema-y)): check-%.json: $(SRC_PATH)/%.json
> -	$(call quiet-command, PYTHONPATH=$(SRC_PATH)/scripts $(PYTHON) $(SRC_PATH)/tests/qapi-schema/test-qapi.py <$^ >$*.test.out 2>$*.test.err; echo $$? >$*.test.exit, "  TEST  $*.out")
> +	$(call quiet-command, PYTHONPATH=$(SRC_PATH)/scripts \
> +		$(PYTHON) $(SRC_PATH)/tests/qapi-schema/test-qapi.py \
> +		<$^ \
> +		>$*.test.out \
> +		2>$*.test.err; \

I've already made the comment several times that I would have put these
three lines as one instead of excessively wrapping into three; I'm a bit
surprised you haven't picked up on the hint when rebasing for other
reasons.  But the patch as-is is still valid, so my Reviewed-by is still
okay whether or not you have a reason to spin a v11.

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

       reply	other threads:[~2014-05-01 12:34 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   ` Eric Blake [this message]
2014-05-02 12:18     ` [Qemu-devel] [PATCH v10 1/4] qapi: [trivial] Break long command lines Lluís Vilanova
     [not found] ` <20140430190946.7884.46553.stgit@fimbulvetr.bsc.es>
2014-05-01 12:37   ` [Qemu-devel] [PATCH v10 3/4] qapi: Use an explicit input file Eric Blake
2014-05-02 12:17     ` 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=53623F50.2000802@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).