| commit | a64d080fff93ba87d399085b56e9e86d28493c79 | |
| author | Elia Pinto <gitter.spiros@gmail.com> | |
| Wed, 23 Dec 2015 13:45:49 +0000 (23 14:45 +0100) | ||
| committer | Junio C Hamano <gitster@pobox.com> | |
| Mon, 28 Dec 2015 21:37:02 +0000 (28 13:37 -0800) | ||
| tree | 8f5520db484cc772cdee38fb76cd83cf327cbb1a | treesnapshot (tar.gz zip) |
| parent | 6ffd3ec88c477bb73e3a149bf6475a1df1a51ab0 | commitdiff |
t/t5303-pack-corruption-resilience.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/t5303-pack-corruption-resilience.sh | diffblobblamehistory |