t/t5510-fetch.sh: use the $( ... ) construct for command substitution
commita9d32be4d28d8f1d0d82788ffd1c3bd6de82931e
authorElia Pinto <gitter.spiros@gmail.com>
Wed, 23 Dec 2015 13:45:55 +0000 (23 14:45 +0100)
committerJunio C Hamano <gitster@pobox.com>
Mon, 28 Dec 2015 21:37:04 +0000 (28 13:37 -0800)
treee4db586bc2185187c905346d72f53502d1cbe4e2
parente15243cc77a58a3038aac3a1977cc8fe0ab45898
t/t5510-fetch.sh: use the $( ... ) construct for command substitution

The Git CodingGuidelines prefer the $(...) construct for command
substitution instead of using the backquotes `...`.

The backquoted form is the traditional method for command
substitution, and is supported by POSIX.  However, all but the
simplest uses become complicated quickly.  In particular, embedded
command substitutions and/or the use of double quotes require
careful escaping with the backslash character.

The patch was generated by:

for _f in $(find . -name "*.sh")
do
perl -i -pe 'BEGIN{undef $/;} s/`(.+?)`/\$(\1)/smg'  "${_f}"
done

and then carefully proof-read.

Signed-off-by: Elia Pinto <gitter.spiros@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
t/t5510-fetch.sh