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 67e0ab3..a9ed84e 100755
--- a/t/
+++ b/t/
@@ -15,7 +15,7 @@ This test checks the following functionality:
 . ./
 mk_empty () {
@@ -421,7 +421,7 @@ test_expect_success 'push tag with non-existent, incomplete 
dest' '
 test_expect_success 'push sha1 with non-existent, incomplete dest' '
        mk_test testrepo &&
-       test_must_fail git push testrepo `git rev-parse master`:foo
+       test_must_fail git push testrepo $(git rev-parse master):foo

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