| commit | 9e5878fbede57c0499133adf73844261849cd7b2 | |
| author | Elia Pinto <gitter.spiros@gmail.com> | |
| Wed, 23 Apr 2014 13:44:02 +0000 (23 06:44 -0700) | ||
| committer | Junio C Hamano <gitster@pobox.com> | |
| Wed, 23 Apr 2014 22:17:02 +0000 (23 15:17 -0700) | ||
| tree | 12b55f759b2a98e677c052003f11f96b8d8cc05a | treesnapshot (tar.gz zip) |
| parent | d0ea45bfc7129304016b24bdb18523b927d0ab17 | commitdiff |
git-web--browse.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
sed -i 's@`\(.*\)`@$(\1)@g' ${_f}
done
and then carefully proof-read.
Signed-off-by: Elia Pinto <gitter.spiros@gmail.com>
Reviewed-by: Matthieu Moy <Matthieu.Moy@imag.fr>
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
sed -i 's@`\(.*\)`@$(\1)@g' ${_f}
done
and then carefully proof-read.
Signed-off-by: Elia Pinto <gitter.spiros@gmail.com>
Reviewed-by: Matthieu Moy <Matthieu.Moy@imag.fr>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
| git-web--browse.sh | diffblobblamehistory |