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.

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

diff --git a/t/ b/t/
index e7cac1d..4216d08 100755
--- a/t/
+++ b/t/
@@ -153,7 +153,7 @@ test_expect_success 'blame path that used to be a 
directory' '
 test_expect_success 'blame to a commit with no author name' '
-  TREE=`git rev-parse HEAD:`
+  TREE=$(git rev-parse HEAD:)
   cat >badcommit <<EOF
 tree $TREE
 author <noname> 1234567890 +0000
@@ -161,7 +161,7 @@ committer David Reiss <> 1234567890 +0000
 some message
-  COMMIT=`git hash-object -t commit -w badcommit`
+  COMMIT=$(git hash-object -t commit -w badcommit)
   git --no-pager blame $COMMIT -- uno >/dev/null

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