t/t5505-remote.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>

Elia Pinto committed Dec 23, 2015 at 14:45 UTC c00978144a523854171aa9ef2857dc16c08d34d4
1 file changed +1 -1
t/t5505-remote.sh
+1 -1
@@ -85,7 +85,7 @@ test_expect_success C_LOCALE_OUTPUT 'check remote-tracking' '
85 test_expect_success 'remote forces tracking branches' '
86 (
87 cd test &&
88 - case `git config remote.second.fetch` in
88 + case $(git config remote.second.fetch) in
89 +*) true ;;
90 *) false ;;
91 esac