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 <redacted>
---
t/t6111-rev-list-treesame.sh | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/t/t6111-rev-list-treesame.sh b/t/t6111-rev-list-treesame.sh
index 88b84df..3971c31 100755
--- a/t/t6111-rev-list-treesame.sh
+++ b/t/t6111-rev-list-treesame.sh
@@ -4,7 +4,7 @@
# / \ / \*
# *A--*B---D--*F-*G---------K-*L-*M
# \ /* \ /
-# `-C-' `-*I-*J
+# $(-C-' )-*I-*J
#
# A creates "file", B and F change it.
# Odd merge G takes the old version from B.
--
1.7.10.4