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 <>
 contrib/subtree/t/ |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/contrib/subtree/t/ 
index 66ce4b0..b22b710 100755
--- a/contrib/subtree/t/
+++ b/contrib/subtree/t/
@@ -76,7 +76,7 @@ test_expect_success 'add sub1' '
 # Save this hash for testing later.
-subdir_hash=`git rev-parse HEAD`
+subdir_hash=$(git rev-parse HEAD)
 test_expect_success 'add sub2' '
         create sub2 &&

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