t9150-svk-mergetickets.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 12, 2016 at 11:49 UTC 9375dcf3b9bb1e462e28d5017165e1c7fa741c77
1 file changed +1 -1
t/t9150-svk-mergetickets.sh
+1 -1
@@ -19,7 +19,7 @@ test_expect_success 'load svk depot' "
19 uuid=b48289b2-9c08-4d72-af37-0358a40b9c15
20
21 test_expect_success 'svk merges were represented coming in' "
22 - [ `git cat-file commit HEAD | grep parent | wc -l` -eq 2 ]
22 + [ $(git cat-file commit HEAD | grep parent | wc -l) -eq 2 ]
23 "
24
25 test_done