t/t2025-worktree-add.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
697b90d7e6de608e616e705c17b8e7395aa5bd70
1 file changed
+2
-2
t/t2025-worktree-add.sh
+2
-2
@@ -123,10 +123,10 @@ test_expect_success 'checkout from a bare repo without "add"' '
123
test_expect_success 'checkout with grafts' '
124
test_when_finished rm .git/info/grafts &&
125
test_commit abc &&
126
- SHA1=`git rev-parse HEAD` &&
126
+ SHA1=$(git rev-parse HEAD) &&
127
test_commit def &&
128
test_commit xyz &&
129
- echo "`git rev-parse HEAD` $SHA1" >.git/info/grafts &&
129
+ echo "$(git rev-parse HEAD) $SHA1" >.git/info/grafts &&
130
cat >expected <<-\EOF &&
131
xyz
132
abc