| commit | 848351b236264631f456fce35c384f892430d3f5 | |
| author | Elia Pinto <gitter.spiros@gmail.com> | |
| Fri, 8 Jan 2016 11:06:20 +0000 (8 12:06 +0100) | ||
| committer | Junio C Hamano <gitster@pobox.com> | |
| Fri, 8 Jan 2016 20:54:05 +0000 (8 12:54 -0800) | ||
| tree | db768d0f1cd6efddf7901145c9abb62c750d53da | treesnapshot (tar.gz zip) |
| parent | 57109790dcf6b2da7bc5e73d31c1dd85c399a6a2 | commitdiff |
t/t7406-submodule-update.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>
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>
| t/t7406-submodule-update.sh | diffblobblamehistory |