The Git CodingGuidelines prefer the $( ... ) construct for command
substitution instead of using the back-quotes, or grave accents (`..`).

The backquoted form is the historical 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. Because of this the POSIX shell adopted the $(…) feature from
the Korn shell.

The patch was generated by the simple script

for _f in $(find . -name "*.sh")
  sed -i 's@`\(.*\)`@$(\1)@g' ${_f}

Signed-off-by: Elia Pinto <>
--- |    4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

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

To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to
More majordomo info at

Reply via email to