From: Mathias Lafeldt <misfire@debugon.org>
To: Junio C Hamano <gitster@pobox.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: [PATCH] t/test-lib.sh: minor readability improvements
Date: Fri, 29 Apr 2011 12:00:35 +0200 [thread overview]
Message-ID: <4DBA8C43.4040804@debugon.org> (raw)
In-Reply-To: <7vmxjb8uyu.fsf@alter.siamese.dyndns.org>
On 04/27/2011 07:28 PM, Junio C Hamano wrote:
> Mathias Lafeldt <misfire@debugon.org> writes:
>
>> Tweak/apply parameter expansion. Also use here document to save
>> test results instead of appending each line with ">>".
>
> Thanks. A few minor nits.
>
>> Signed-off-by: Mathias Lafeldt <misfire@debugon.org>
>> ---
>> t/test-lib.sh | 18 ++++++++++--------
>> 1 files changed, 10 insertions(+), 8 deletions(-)
>>
>> diff --git a/t/test-lib.sh b/t/test-lib.sh
>> index abc47f3..b30725f 100644
>> --- a/t/test-lib.sh
>> +++ b/t/test-lib.sh
>> @@ -24,7 +24,7 @@ done,*)
>> *' --tee '*|*' --va'*)
>> mkdir -p test-results
>> BASE=test-results/$(basename "$0" .sh)
>> - (GIT_TEST_TEE_STARTED=done ${SHELL-sh} "$0" "$@" 2>&1;
>> + (GIT_TEST_TEE_STARTED=done ${SHELL-"sh"} "$0" "$@" 2>&1;
>
> Looks unnecessary. Superstition?
IMHO, ${SHELL-sh} is kind of hard to read, especially when you
don't know about the ${parameter-word} format. In hindsight, I
understand that the change isn't really necessary.
>> echo $? > $BASE.exit) | tee $BASE.out
>> test "$(cat $BASE.exit)" = 0
>> exit
>> @@ -575,7 +575,7 @@ test_external () {
>> test_external_without_stderr () {
>> # The temporary file has no (and must have no) security
>> # implications.
>> - tmp="$TMPDIR"; if [ -z "$tmp" ]; then tmp=/tmp; fi
>> + tmp=${TMPDIR:-"/tmp"}
I guess, you'd prefer ${TMPDIR:-/tmp} here too.
>> stderr="$tmp/git-external-stderr.$$.tmp"
>> test_external "$@" 4> "$stderr"
>> [ -f "$stderr" ] || error "Internal error: $stderr disappeared."
>> @@ -801,12 +801,14 @@ test_done () {
>> mkdir -p "$test_results_dir"
>> test_results_path="$test_results_dir/${0%.sh}-$$.counts"
>>
>> - echo "total $test_count" >> $test_results_path
>> - echo "success $test_success" >> $test_results_path
>> - echo "fixed $test_fixed" >> $test_results_path
>> - echo "broken $test_broken" >> $test_results_path
>> - echo "failed $test_failure" >> $test_results_path
>> - echo "" >> $test_results_path
>> + cat >> "$test_results_path" <<EOF
>> +total $test_count
>> +success $test_success
>> +fixed $test_fixed
>> +broken $test_broken
>> +failed $test_failure
>> +
>> +EOF
>
> It may probably be even easier to read if you indented the whole thing,
> using the dash before the here-doc marker, like so:
>
> cat >>"$test_results_path" <<-EOF
> total $test_count
> success $test_success
> ...
> EOF
OK, I'll be re-rolling the patch using "<<-EOF".
-Mathias
next prev parent reply other threads:[~2011-04-29 10:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-27 12:49 [PATCH] t/test-lib.sh: minor readability improvements Mathias Lafeldt
2011-04-27 17:28 ` Junio C Hamano
2011-04-29 10:00 ` Mathias Lafeldt [this message]
2011-04-29 12:30 ` [PATCH v2] " Mathias Lafeldt
2011-04-29 16:28 ` Junio C Hamano
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=4DBA8C43.4040804@debugon.org \
--to=misfire@debugon.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).