git-fetch.sh: use the $( ... ) construct for command substitution
commit3e867415170ed73511291fb2dd47bac3c4d51f3a
authorElia Pinto <gitter.spiros@gmail.com>
Wed, 16 Apr 2014 17:29:50 +0000 (16 10:29 -0700)
committerJunio C Hamano <gitster@pobox.com>
Thu, 17 Apr 2014 18:14:59 +0000 (17 11:14 -0700)
treeee50039d7cd407cb06329962fbb83d04f5d0db21
parent346b54dbc92bb3c928d326da9d8addf5eb50acce
git-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
   sed -i 's@`\(.*\)`@$(\1)@g' ${_f}
done

and then carefully proof-read.

Signed-off-by: Elia Pinto <gitter.spiros@gmail.com>
Reviewed-by: Matthieu Moy <Matthieu.Moy@imag.fr>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
contrib/examples/git-fetch.sh