t/t1700-split-index.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> Reviewed-by: Jonathan Nieder <jrnieder@gmail.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>

Elia Pinto committed Dec 22, 2015 at 16:05 UTC 16149d75bdc638efb7412baa9d24e5b1c39f58f3
1 file changed +1 -1
t/t1700-split-index.sh
+1 -1
@@ -55,7 +55,7 @@ test_expect_success 'disable split index' '
55 EOF
56 test_cmp ls-files.expect ls-files.actual &&
57
58 - BASE=`test-dump-split-index .git/index | grep "^own" | sed "s/own/base/"` &&
58 + BASE=$(test-dump-split-index .git/index | grep "^own" | sed "s/own/base/") &&
59 test-dump-split-index .git/index | sed "/^own/d" >actual &&
60 cat >expect <<EOF &&
61 not a split index