summaryrefslogtreecommitdiff
path: root/t/t3510-cherry-pick-sequence.sh
diff options
context:
space:
mode:
authorLibravatar Elia Pinto <gitter.spiros@gmail.com>2016-01-08 12:06:22 +0100
committerLibravatar Junio C Hamano <gitster@pobox.com>2016-01-08 12:54:06 -0800
commit33c85913dffb9a2328a97f0ac5c15609f9a64e28 (patch)
tree5bc9396d891baeec21db8129a5676fb8bdae838a /t/t3510-cherry-pick-sequence.sh
parentt/t7408-submodule-reference.sh: use the $( ... ) construct for command substi... (diff)
downloadtgif-33c85913dffb9a2328a97f0ac5c15609f9a64e28.tar.xz
t/t7504-commit-msg-hook.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/t3510-cherry-pick-sequence.sh')
0 files changed, 0 insertions, 0 deletions