t/t7504-commit-msg-hook.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 8, 2016 at 12:06 UTC
33c85913dffb9a2328a97f0ac5c15609f9a64e28
1 file changed
+1
-1
t/t7504-commit-msg-hook.sh
+1
-1
@@ -179,7 +179,7 @@ EOF
179
chmod +x "$HOOK"
180
181
commit_msg_is () {
182
- test "`git log --pretty=format:%s%b -1`" = "$1"
182
+ test "$(git log --pretty=format:%s%b -1)" = "$1"
183
}
184
185
test_expect_success 'hook edits commit message' '