t/t7505-prepare-commit-msg-hook.sh: use the $( ... ) construct for command substitution
commit0c923256a0116c2729a78dc01dfe223a67d7a95b
authorElia Pinto <gitter.spiros@gmail.com>
Fri, 8 Jan 2016 11:06:23 +0000 (8 12:06 +0100)
committerJunio C Hamano <gitster@pobox.com>
Fri, 8 Jan 2016 20:54:06 +0000 (8 12:54 -0800)
treed26c646134045b5868b535323e68f384b18b3740
parent33c85913dffb9a2328a97f0ac5c15609f9a64e28
t/t7505-prepare-commit-msg-hook.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/t7505-prepare-commit-msg-hook.sh