diff options
author | Elia Pinto <gitter.spiros@gmail.com> | 2016-01-12 11:49:34 +0000 |
---|---|---|
committer | Junio C Hamano <gitster@pobox.com> | 2016-01-12 11:49:47 -0800 |
commit | 9375dcf3b9bb1e462e28d5017165e1c7fa741c77 (patch) | |
tree | 412216fe4262934389280157b033551244c90555 /t/t6021-merge-criss-cross.sh | |
parent | t9145-git-svn-master-branch.sh: use the $( ... ) construct for command substi... (diff) | |
download | tgif-9375dcf3b9bb1e462e28d5017165e1c7fa741c77.tar.xz |
t9150-svk-mergetickets.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/t6021-merge-criss-cross.sh')
0 files changed, 0 insertions, 0 deletions