| commit | 86e30432177470f50be4207da2cc0422f86a24f7 | |
| author | Elia Pinto <gitter.spiros@gmail.com> | |
| Mon, 28 Apr 2014 12:57:31 +0000 (28 05:57 -0700) | ||
| committer | Junio C Hamano <gitster@pobox.com> | |
| Tue, 29 Apr 2014 19:44:30 +0000 (29 12:44 -0700) | ||
| tree | 2a468248597699da5a12f2c883b0185550df7a65 | treesnapshot (tar.gz zip) |
| parent | dd64267fe2151b1ea3f19b5745d0fa8321995381 | commitdiff |
t1000-read-tree-m-3way.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>
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>
| t/t1000-read-tree-m-3way.sh | diffblobblamehistory |