| commit | 9b4950899aa6a910644d35c2b6cd475d83c7af17 | |
| author | Elia Pinto <gitter.spiros@gmail.com> | |
| Tue, 22 Dec 2015 15:27:47 +0000 (22 16:27 +0100) | ||
| committer | Junio C Hamano <gitster@pobox.com> | |
| Mon, 28 Dec 2015 21:36:32 +0000 (28 13:36 -0800) | ||
| tree | de7f79c8c68e3c0615c93d7cf3c581b92cfbd690 | treesnapshot (tar.gz zip) |
| parent | c82ec45e8673470ba270ae19887c43553553c50e | commitdiff |
t/t3511-cherry-pick-x.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/t3511-cherry-pick-x.sh | diffblobblamehistory |