t/t7001-mv.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 7, 2016 at 14:51 UTC
36b4697fdcc1acbe3cda7d67f6f371ebe9d4f018
1 file changed
+2
-2
t/t7001-mv.sh
+2
-2
@@ -156,11 +156,11 @@ test_expect_success "Michael Cassar's test case" '
156
echo b > partA/outline.txt &&
157
echo c > papers/unsorted/_another &&
158
git add papers partA &&
159
- T1=`git write-tree` &&
159
+ T1=$(git write-tree) &&
160
161
git mv papers/unsorted/Thesis.pdf papers/all-papers/moo-blah.pdf &&
162
163
- T=`git write-tree` &&
163
+ T=$(git write-tree) &&
164
git ls-tree -r $T | verbose grep partA/outline.txt
165
'
166