| commit | f25f5e61a7c1a22dd85413d61db639e7c01268f4 | |
| author | Elia Pinto <gitter.spiros@gmail.com> | |
| Wed, 16 Apr 2014 17:29:45 +0000 (16 10:29 -0700) | ||
| committer | Junio C Hamano <gitster@pobox.com> | |
| Thu, 17 Apr 2014 18:14:57 +0000 (17 11:14 -0700) | ||
| tree | 9100b6ea8d6bdc6d05c84efbdf56912f7bf40ed8 | treesnapshot (tar.gz zip) |
| parent | 75ee3d7078fbcc3b87a3ae5e0cf42f46256c5da4 | commitdiff |
howto-index.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>
| Documentation/howto-index.sh | diffblobblamehistory |