summaryrefslogtreecommitdiff
path: root/t/t2100-update-cache-badpath.sh
diff options
context:
space:
mode:
authorLibravatar Elia Pinto <gitter.spiros@gmail.com>2016-01-12 11:49:33 +0000
committerLibravatar Junio C Hamano <gitster@pobox.com>2016-01-12 11:49:47 -0800
commite74ef604974192712c38f77cd751b00ad36e1378 (patch)
tree0a2223ac2bc7ca74151886606a0b7adea1362b07 /t/t2100-update-cache-badpath.sh
parentt9138-git-svn-authors-prog.sh: use the $( ... ) construct for command substit... (diff)
downloadtgif-e74ef604974192712c38f77cd751b00ad36e1378.tar.xz
t9145-git-svn-master-branch.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 't/t2100-update-cache-badpath.sh')
0 files changed, 0 insertions, 0 deletions