t/t5601-clone.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 Jan 4, 2016 at 10:10 UTC c723e50d413882c5196e823312f2743a96d7d8c3
1 file changed +1 -1
t/t5601-clone.sh
+1 -1
@@ -221,7 +221,7 @@ test_expect_success 'clone separate gitdir' '
221 '
222
223 test_expect_success 'clone separate gitdir: output' '
224 - echo "gitdir: `pwd`/realgitdir" >expected &&
224 + echo "gitdir: $(pwd)/realgitdir" >expected &&
225 test_cmp expected dst/.git
226 '
227