qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Eric Blake <eblake@redhat.com>
To: unai.martinezcorral@ehu.eus
Cc: qemu-devel@nongnu.org, riku.voipio@iki.fi, laurent@vivier.eu
Subject: Re: [Qemu-devel] [PATCH] qemu-binfmt-conf.sh: add CPUS, add --reset, make -p and -c boolean (no arg)
Date: Tue, 5 Mar 2019 13:57:52 -0600	[thread overview]
Message-ID: <0f1615fd-6cb7-2959-aae5-e811286e95b3@redhat.com> (raw)
In-Reply-To: <CAGZZdDH1CvhvJ7ZoCGgc8wYgk01ePn_7VnWdacaEkRVNSMTxvA@mail.gmail.com>

On 3/5/19 1:36 PM, Unai Martinez Corral wrote:
> 2019/3/5 17:57, Eric Blake:
>> You are correct that 'printf -1' is likely to fail, 'printf -- -1' is
>> portable but unusual, and 'printf %s\\n -1' is identical to the common
>> (but non-portable) behavior of 'echo -1'. Is the newline important?
> 
> In this case, the newline seems not to be relevant. I find 'printf --
> -1' elegant, but since I already submitted v2 of the patch, I think
> the difference compared to 'printf %s -1' is not worth a new version.
> Please, let me know if you feel otherwise.

I don't have a strong preference between the two forms - so this is your 
chance to assert your creative liberty. But I don't know enough about 
binfmt_misc to know if the newline matters. I'm just reviewing on the 
basis of shell portability, and hope that other reviewers more familiar 
with binfmt will review on content. That said, I already have enough 
other comments on v2 that you may want to split this into a series of 
patches for v3, although you could also wait a day or so to see if 
anyone else reviews and minimize the list churn.

-- 
Eric Blake, Principal Software Engineer
Red Hat, Inc.           +1-919-301-3226
Virtualization:  qemu.org | libvirt.org

  reply	other threads:[~2019-03-05 19:57 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-05  6:28 [Qemu-devel] [PATCH] qemu-binfmt-conf.sh: add CPUS, add --reset, make -p and -c boolean (no arg) Unai Martinez Corral
2019-03-05 15:35 ` Unai Martinez Corral
2019-03-05 16:44 ` Unai Martinez Corral
2019-03-05 16:57 ` Eric Blake
2019-03-05 19:15   ` Unai Martinez Corral
2019-03-05 19:20     ` Eric Blake
2019-03-05 19:36       ` Unai Martinez Corral
2019-03-05 19:57         ` Eric Blake [this message]
2019-03-05 19:32     ` [Qemu-devel] [PATCH v2] " Unai Martinez Corral
2019-03-05 19:54       ` Eric Blake
2019-03-05 20:28         ` Unai Martinez Corral

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=0f1615fd-6cb7-2959-aae5-e811286e95b3@redhat.com \
    --to=eblake@redhat.com \
    --cc=laurent@vivier.eu \
    --cc=qemu-devel@nongnu.org \
    --cc=riku.voipio@iki.fi \
    --cc=unai.martinezcorral@ehu.eus \
    /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).