| commit | ce21ccfae0729fd73b54f3ae4935fc7769343561 | |
| author | Elia Pinto <gitter.spiros@gmail.com> | |
| Wed, 30 Apr 2014 16:23:06 +0000 (30 09:23 -0700) | ||
| committer | Junio C Hamano <gitster@pobox.com> | |
| Wed, 30 Apr 2014 18:08:09 +0000 (30 11:08 -0700) | ||
| tree | bcd8bcc5770ccbb3322c3201e5f6c359a4ca85fb | treesnapshot (tar.gz zip) |
| parent | 6003eb13c69516dfedc9466aeb8c3a32a054c286 | commitdiff |
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>
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/t4204-patch-id.sh | diffblobblamehistory |