summaryrefslogtreecommitdiff
path: root/Documentation/git-replace.txt
diff options
context:
space:
mode:
authorLibravatar Elia Pinto <gitter.spiros@gmail.com>2014-04-23 06:43:53 -0700
committerLibravatar Junio C Hamano <gitster@pobox.com>2014-04-23 15:17:01 -0700
commit9bfeaa0bcf2d7150836b583196e18f973c3be17f (patch)
tree3f610009b1cd9345d1173eb454cd8d75d1bad65b /Documentation/git-replace.txt
parentt9362-mw-to-git-utf8.sh: use the $( ... ) construct for command substitution (diff)
downloadtgif-9bfeaa0bcf2d7150836b583196e18f973c3be17f.tar.xz
t9365-continuing-queries.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 'Documentation/git-replace.txt')
0 files changed, 0 insertions, 0 deletions