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 <>
 t/ |    4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/t/ b/t/
index e3c8c2c..23564bf 100755
--- a/t/
+++ b/t/
@@ -156,11 +156,11 @@ test_expect_success "Michael Cassar's test case" '
        echo b > partA/outline.txt &&
        echo c > papers/unsorted/_another &&
        git add papers partA &&
-       T1=`git write-tree` &&
+       T1=$(git write-tree) &&
        git mv papers/unsorted/Thesis.pdf papers/all-papers/moo-blah.pdf &&
-       T=`git write-tree` &&
+       T=$(git write-tree) &&
        git ls-tree -r $T | grep partA/outline.txt || {
                git ls-tree -r $T
                (exit 1)

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