check-builtins.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>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
This commit is contained in:
Elia Pinto 2014-03-25 10:22:22 -07:00 committed by Junio C Hamano
parent d393d140b5
commit b09d8552bd

View File

@ -14,8 +14,8 @@ sort |
bad=0 bad=0
while read builtin while read builtin
do do
base=`expr "$builtin" : 'git-\(.*\)'` base=$(expr "$builtin" : 'git-\(.*\)')
x=`sed -ne 's/.*{ "'$base'", \(cmd_[^, ]*\).*/'$base' \1/p' git.c` x=$(sed -ne 's/.*{ "'$base'", \(cmd_[^, ]*\).*/'$base' \1/p' git.c)
if test -z "$x" if test -z "$x"
then then
echo "$base is builtin but not listed in git.c command list" echo "$base is builtin but not listed in git.c command list"