From: Max Reitz <mreitz@redhat.com>
To: Eric Blake <eblake@redhat.com>, qemu-devel@nongnu.org
Cc: kwolf@redhat.com, stefanha@redhat.com,
Jiri Pirko <jiri@resnulli.us>,
"Edgar E. Iglesias" <edgar.iglesias@gmail.com>,
"open list:Block layer core" <qemu-block@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] tests: Avoid non-portable 'echo -ARG'
Date: Fri, 30 Jun 2017 16:38:46 +0200 [thread overview]
Message-ID: <a83183bc-464c-dd5b-aff9-fff07bde833c@redhat.com> (raw)
In-Reply-To: <20170628142137.7440-1-eblake@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 2009 bytes --]
On 2017-06-28 16:21, Eric Blake wrote:
> POSIX says that backslashes in the arguments to 'echo', as well as
> any use of 'echo -n' and 'echo -e', are non-portable; it recommends
> people should favor 'printf' instead. This is definitely true where
> we do not control which shell is running (such as in makefile snippets
> or in documentation examples). But even for scripts where we
> require bash (and therefore, where echo does what we want by default),
> it is still possible to use 'shopt -s xpg_echo' to change bash's
> behavior of echo. And setting a good example never hurts when we are
> not sure if a snippet will be copied from a bash-only script to a
> general shell script (although I don't change the use of non-portable
> \e for ESC when we know the running shell is bash).
>
> Replace 'echo -n "..."' with 'printf "..."', and 'echo -e "..."'
> with 'printf "...\n"'.
>
> In the qemu-iotests check script, also fix unusual shell quoting
> that would result in word-splitting if 'date' outputs a space.
>
> Signed-off-by: Eric Blake <eblake@redhat.com>
> ---
>
> Of course, Stefan's pending patch:
> [PATCH 3/5] qemu-iotests: 068: extract _qemu() function
> also touches 068, so there may be some (obvious) merge conflicts
> to resolve there depending on what goes in first.
>
> qemu-options.hx | 4 ++--
> tests/multiboot/run_test.sh | 10 +++++-----
> tests/qemu-iotests/051 | 7 ++++---
> tests/qemu-iotests/068 | 2 +-
> tests/qemu-iotests/142 | 48 ++++++++++++++++++++++-----------------------
> tests/qemu-iotests/171 | 14 ++++++-------
> tests/qemu-iotests/check | 18 ++++++++---------
> tests/rocker/all | 10 +++++-----
> tests/tcg/cris/Makefile | 8 ++++----
> 9 files changed, 61 insertions(+), 60 deletions(-)
Question 1: Who's going to take this? :-)
Question 2: This breaks 171 if TEST_DIR contains a % (e.g.
"TEST_DIR=/tmp/foo%% ./check -raw 171"). Is that OK?
Max
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 498 bytes --]
next prev parent reply other threads:[~2017-06-30 14:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-28 14:21 [Qemu-devel] [PATCH] tests: Avoid non-portable 'echo -ARG' Eric Blake
2017-06-28 14:46 ` Edgar E. Iglesias
2017-06-30 10:02 ` Stefan Hajnoczi
2017-06-30 14:38 ` Max Reitz [this message]
2017-06-30 14:44 ` Eric Blake
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=a83183bc-464c-dd5b-aff9-fff07bde833c@redhat.com \
--to=mreitz@redhat.com \
--cc=eblake@redhat.com \
--cc=edgar.iglesias@gmail.com \
--cc=jiri@resnulli.us \
--cc=kwolf@redhat.com \
--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).