summaryrefslogtreecommitdiff
path: root/t/t9603-cvsimport-patchsets.sh
diff options
context:
space:
mode:
authorLibravatar Elia Pinto <gitter.spiros@gmail.com>2015-12-22 16:05:50 +0100
committerLibravatar Junio C Hamano <gitster@pobox.com>2015-12-27 15:44:49 -0800
commitdcfbb2aa891a15fd647ca03f54093c9867ea4f44 (patch)
tree00e4e5f40c7afcbe793c054409f1336499561f4f /t/t9603-cvsimport-patchsets.sh
parentt/t1511-rev-parse-caret.sh: use the $( ... ) construct for command substitution (diff)
downloadtgif-dcfbb2aa891a15fd647ca03f54093c9867ea4f44.tar.xz
t/t1512-rev-parse-disambiguation.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 't/t9603-cvsimport-patchsets.sh')
0 files changed, 0 insertions, 0 deletions