diff options
author | Elia Pinto <gitter.spiros@gmail.com> | 2014-04-16 10:29:58 -0700 |
---|---|---|
committer | Junio C Hamano <gitster@pobox.com> | 2014-04-17 11:15:01 -0700 |
commit | bd368a9baf5a42e2076ef4c8a35312ccab171452 (patch) | |
tree | c1fa83f7abbb15d4b084ef482dca3cafdc3ac685 /git-merge-resolve.sh | |
parent | t9360-mw-to-git-clone.sh: use the $( ... ) construct for command substitution (diff) | |
download | tgif-bd368a9baf5a42e2076ef4c8a35312ccab171452.tar.xz |
t9362-mw-to-git-utf8.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
sed -i 's@`\(.*\)`@$(\1)@g' ${_f}
done
and then carefully proof-read.
Signed-off-by: Elia Pinto <gitter.spiros@gmail.com>
Reviewed-by: Matthieu Moy <Matthieu.Moy@imag.fr>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'git-merge-resolve.sh')
0 files changed, 0 insertions, 0 deletions