| commit | 9bfeaa0bcf2d7150836b583196e18f973c3be17f | |
| author | Elia Pinto <gitter.spiros@gmail.com> | |
| Wed, 23 Apr 2014 13:43:53 +0000 (23 06:43 -0700) | ||
| committer | Junio C Hamano <gitster@pobox.com> | |
| Wed, 23 Apr 2014 22:17:01 +0000 (23 15:17 -0700) | ||
| tree | 3f610009b1cd9345d1173eb454cd8d75d1bad65b | treesnapshot (tar.gz zip) |
| parent | bd368a9baf5a42e2076ef4c8a35312ccab171452 | commitdiff |
t9365-continuing-queries.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>
| contrib/mw-to-git/t/t9365-continuing-queries.sh | diffblobblamehistory |