summaryrefslogtreecommitdiff
path: root/contrib/examples/git-merge.sh
diff options
context:
space:
mode:
authorElia Pinto <gitter.spiros@gmail.com>2015-12-22 14:10:23 (GMT)
committerJunio C Hamano <gitster@pobox.com>2015-12-27 23:33:13 (GMT)
commita22c9e8d9e29277f51b77aff8d0eee3945577e72 (patch)
tree86a75e3ea77e8875fb667623a5d434c8b63a723e /contrib/examples/git-merge.sh
parent554f6e41067b9e3e565b6988a8294fac1cb78f4b (diff)
downloadgit-a22c9e8d9e29277f51b77aff8d0eee3945577e72.zip
git-a22c9e8d9e29277f51b77aff8d0eee3945577e72.tar.gz
git-a22c9e8d9e29277f51b77aff8d0eee3945577e72.tar.bz2
contrib/examples/git-commit.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 'contrib/examples/git-merge.sh')
0 files changed, 0 insertions, 0 deletions