summaryrefslogtreecommitdiff
path: root/compat
diff options
context:
space:
mode:
authorLibravatar Elia Pinto <gitter.spiros@gmail.com>2016-01-12 10:45:17 +0000
committerLibravatar Junio C Hamano <gitster@pobox.com>2016-01-12 11:47:29 -0800
commit78ba28d84b5be8cbb1d5d5e7d65b5522739ad5ce (patch)
treec6fa72b7d07c6a9697d66b56c9f47194e218a8fa /compat
parentt9110-git-svn-use-svm-props.sh: use the $( ... ) construct for command substi... (diff)
downloadtgif-78ba28d84b5be8cbb1d5d5e7d65b5522739ad5ce.tar.xz
t9114-git-svn-dcommit-merge.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 'compat')
0 files changed, 0 insertions, 0 deletions