| commit | 8a7b73c1527c1bcad3230c791b8761a5101abf8d | |
| author | Elia Pinto <gitter.spiros@gmail.com> | |
| Tue, 22 Dec 2015 15:05:47 +0000 (22 16:05 +0100) | ||
| committer | Junio C Hamano <gitster@pobox.com> | |
| Sun, 27 Dec 2015 23:44:49 +0000 (27 15:44 -0800) | ||
| tree | e49793cd9f666c00d4829a20f5fc37d2c35e1fb6 | treesnapshot (tar.gz zip) |
| parent | cbda02fcb7254029f0f5cb4a0ce623700da01b00 | commitdiff |
t/t1401-symbolic-ref.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>
Reviewed-by: Jonathan Nieder <jrnieder@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>
Reviewed-by: Jonathan Nieder <jrnieder@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
| t/t1401-symbolic-ref.sh | diffblobblamehistory |