summaryrefslogtreecommitdiff
path: root/README
diff options
context:
space:
mode:
authorLibravatar Elia Pinto <gitter.spiros@gmail.com>2016-01-12 10:45:12 +0000
committerLibravatar Junio C Hamano <gitster@pobox.com>2016-01-12 11:47:27 -0800
commit32858a01506b22963cfd5f8c8db95486f26133af (patch)
tree6ca3bbc5a9b913892a2df4e20c1d4e6524078262 /README
parentt9104-git-svn-follow-parent.sh: use the $( ... ) construct for command substi... (diff)
downloadtgif-32858a01506b22963cfd5f8c8db95486f26133af.tar.xz
t9105-git-svn-commit-diff.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>
Diffstat (limited to 'README')
0 files changed, 0 insertions, 0 deletions