| commit | 9375dcf3b9bb1e462e28d5017165e1c7fa741c77 | |
| author | Elia Pinto <gitter.spiros@gmail.com> | |
| Tue, 12 Jan 2016 11:49:34 +0000 (12 11:49 +0000) | ||
| committer | Junio C Hamano <gitster@pobox.com> | |
| Tue, 12 Jan 2016 19:49:47 +0000 (12 11:49 -0800) | ||
| tree | 412216fe4262934389280157b033551244c90555 | treesnapshot (tar.gz zip) |
| parent | e74ef604974192712c38f77cd751b00ad36e1378 | commitdiff |
t9150-svk-mergetickets.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/t9150-svk-mergetickets.sh | diffblobblamehistory |