| commit | 57da04965d56c7d7da6a00c3fb6fc3981cf0ba9a | |
| author | Elia Pinto <gitter.spiros@gmail.com> | |
| Tue, 12 Jan 2016 11:49:27 +0000 (12 11:49 +0000) | ||
| committer | Junio C Hamano <gitster@pobox.com> | |
| Tue, 12 Jan 2016 19:49:46 +0000 (12 11:49 -0800) | ||
| tree | 2f0010ed754945adcb7d3aac71750ddd821fd93f | treesnapshot (tar.gz zip) |
| parent | 1d9e86f80d2ede6829c57ef4b22e4dd8b162cc7e | commitdiff |
t9119-git-svn-info.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/t9119-git-svn-info.sh | diffblobblamehistory |