| commit | c7b793a17d92350632c51a24e06b6a3dc4a93c2b | |
| author | Elia Pinto <gitter.spiros@gmail.com> | |
| Tue, 12 Jan 2016 11:49:36 +0000 (12 11:49 +0000) | ||
| committer | Junio C Hamano <gitster@pobox.com> | |
| Tue, 12 Jan 2016 19:49:48 +0000 (12 11:49 -0800) | ||
| tree | 66618aee74e8060fd92786ad93734dba04f59461 | treesnapshot (tar.gz zip) |
| parent | 80a6b3f0d54d0df6c6994df5486433bf0b9a54c0 | commitdiff |
t9350-fast-export.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/t9350-fast-export.sh | diffblobblamehistory |