| commit | 14a771eee9a0ddcab08da42580e0f32d0e89b284 | |
| author | Elia Pinto <gitter.spiros@gmail.com> | |
| Thu, 7 Jan 2016 13:51:41 +0000 (7 14:51 +0100) | ||
| committer | Junio C Hamano <gitster@pobox.com> | |
| Thu, 7 Jan 2016 21:56:32 +0000 (7 13:56 -0800) | ||
| tree | 34a053323b20fdf54160af829d604094a79f6859 | treesnapshot (tar.gz zip) |
| parent | 7438e3f64a8620ec549f078f5e4f67ebd1d8b76a | commitdiff |
t/t5900-repo-selection.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/t5900-repo-selection.sh | diffblobblamehistory |