]> git.ipfire.org Git - thirdparty/git.git/commit - t/t5515-fetch-merge-logic.sh
t/t5515-fetch-merge-logic.sh: use the $( ... ) construct for command substitution
authorElia Pinto <gitter.spiros@gmail.com>
Wed, 23 Dec 2015 13:45:56 +0000 (14:45 +0100)
committerJunio C Hamano <gitster@pobox.com>
Mon, 28 Dec 2015 21:37:04 +0000 (13:37 -0800)
commit28666e55f3bc3f7731a58085f23f21d38ec005f4
treee1f3b7a2a4390f17a0629f9bafc09e6fdf68c2a1
parenta9d32be4d28d8f1d0d82788ffd1c3bd6de82931e
t/t5515-fetch-merge-logic.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/t5515-fetch-merge-logic.sh