| commit | fc7b076d33db9886c5cfe8639d9a7e37159606ac | |
| author | Elia Pinto <gitter.spiros@gmail.com> | |
| Tue, 22 Dec 2015 15:27:50 +0000 (22 16:27 +0100) | ||
| committer | Junio C Hamano <gitster@pobox.com> | |
| Mon, 28 Dec 2015 21:36:41 +0000 (28 13:36 -0800) | ||
| tree | d9ca56430ff3489ec8020f169a98b46d5bd6d898 | treesnapshot (tar.gz zip) |
| parent | ed6c23142a03269d73e720b05d4968652e1b3cb8 | commitdiff |
t/t5100-mailinfo.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/t5100-mailinfo.sh | diffblobblamehistory |