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")
   sed -i 's@`\(.*\)`@$(\1)@g' ${_f}

and then carefully proof-read.

Signed-off-by: Elia Pinto <>
 t/ |    6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/t/ b/t/
index e77c09c..805b055 100755
--- a/t/
+++ b/t/
@@ -107,14 +107,14 @@ test_expect_success setup '
 +*++ [initial] Initial
-V=`git version | sed -e 's/^git version //' -e 's/\./\\./g'`
+V=$(git version | sed -e 's/^git version //' -e 's/\./\\./g')
 while read cmd
        case "$cmd" in
        '' | '#'*) continue ;;
-       test=`echo "$cmd" | sed -e 's|[/ ][/ ]*|_|g'`
-       pfx=`printf "%04d" $test_count`
+       test=$(echo "$cmd" | sed -e 's|[/ ][/ ]*|_|g')
+       pfx=$(printf "%04d" $test_count)

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