diff options
author | Elia Pinto <gitter.spiros@gmail.com> | 2015-12-22 15:10:24 +0100 |
---|---|---|
committer | Junio C Hamano <gitster@pobox.com> | 2015-12-27 15:33:13 -0800 |
commit | cc301d7e5193801208588cbd54cf1af91b6f7a00 (patch) | |
tree | 5fc0d64ffe69f584141f70e1a642232115a7d6a5 /diffcore-pickaxe.c | |
parent | contrib/examples/git-commit.sh: use the $( ... ) construct for command substi... (diff) | |
download | tgif-cc301d7e5193801208588cbd54cf1af91b6f7a00.tar.xz |
contrib/examples/git-fetch.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>
Diffstat (limited to 'diffcore-pickaxe.c')
0 files changed, 0 insertions, 0 deletions