t4204-patch-id.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
sed -i 's@`\(.*\)`@$(\1)@g' ${_f}
done
and then carefully proof-read.
Signed-off-by: Elia Pinto <gitter.spiros@gmail.com>
Reviewed-by: Matthieu Moy <Matthieu.Moy@imag.fr>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
maint
parent
6003eb13c6
commit
ce21ccfae0
|
|
@ -45,8 +45,8 @@ test_expect_success 'patch-id supports git-format-patch output' '
|
|||
git checkout same &&
|
||||
git format-patch -1 --stdout | calc_patch_id same &&
|
||||
test_cmp patch-id_master patch-id_same &&
|
||||
set `git format-patch -1 --stdout | git patch-id` &&
|
||||
test "$2" = `git rev-parse HEAD`
|
||||
set $(git format-patch -1 --stdout | git patch-id) &&
|
||||
test "$2" = $(git rev-parse HEAD)
|
||||
'
|
||||
|
||||
test_expect_success 'whitespace is irrelevant in footer' '
|
||||
|
|
|
|||
Loading…
Reference in New Issue