| commit | 91852b50a6366283652535b8eca940e72c205138 | |
| author | Elia Pinto <gitter.spiros@gmail.com> | |
| Mon, 4 Jan 2016 09:10:42 +0000 (4 10:10 +0100) | ||
| committer | Junio C Hamano <gitster@pobox.com> | |
| Mon, 4 Jan 2016 21:41:44 +0000 (4 13:41 -0800) | ||
| tree | 77f8e4f9f2d487e31067e781913de5c39025b28c | treesnapshot (tar.gz zip) |
| parent | 5ee0d624fbb1f3874067776cb9cdecdbbcdd6b84 | commitdiff |
t/t5522-pull-symlink.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/t5522-pull-symlink.sh | diffblobblamehistory |