git/list[1] front-page[2] threads[3] people[4] search[5] about
 

[PATCH 03/10] t/t1410-reflog.sh: use the $( ... ) construct for command substitution

From
Elia Pinto <gitter.spiros@gmail.com>
Date
Dec 22, 2015, 15:05 UTC
Message-ID
<1450796755-15848-4-git-send-email-gitter.spiros@gmail.com>
In-Reply-To
<1450796755-15848-1-git-send-email-gitter.spiros@gmail.com>

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")
do
	perl -i -pe 'BEGIN{undef $/;} s/`(.+?)`/\$(\1)/smg'  "${_f}"
done
and then carefully proof-read.
Signed-off-by: Elia Pinto <gitter.spiros@gmail.com>
---
 t/t1410-reflog.sh | 24 ++++++++++++------------
 1 file changed, 12 insertions(+), 12 deletions(-)
diff --git a/t/t1410-reflog.sh b/t/t1410-reflog.sh
index b79049f..fbed8d7 100755
--- a/t/t1410-reflog.sh
+++ b/t/t1410-reflog.sh
@@ -62,18 +62,18 @@ test_expect_success setup '
 	git add . &&
 
 	test_tick && git commit -m rabbit &&
-	H=`git rev-parse --verify HEAD` &&
-	A=`git rev-parse --verify HEAD:A` &&
-	B=`git rev-parse --verify HEAD:A/B` &&
-	C=`git rev-parse --verify HEAD:C` &&
-	D=`git rev-parse --verify HEAD:A/D` &&
-	E=`git rev-parse --verify HEAD:A/B/E` &&
+	H=$(git rev-parse --verify HEAD) &&
+	A=$(git rev-parse --verify HEAD:A) &&
+	B=$(git rev-parse --verify HEAD:A/B) &&
+	C=$(git rev-parse --verify HEAD:C) &&
+	D=$(git rev-parse --verify HEAD:A/D) &&
+	E=$(git rev-parse --verify HEAD:A/B/E) &&
 	check_fsck &&
 
 	test_chmod +x C &&
 	git add C &&
 	test_tick && git commit -m dragon &&
-	L=`git rev-parse --verify HEAD` &&
+	L=$(git rev-parse --verify HEAD) &&
 	check_fsck &&
 
 	rm -f C A/B/E &&
@@ -81,15 +81,15 @@ test_expect_success setup '
 	echo horse >A/G &&
 	git add F A/G &&
 	test_tick && git commit -a -m sheep &&
-	F=`git rev-parse --verify HEAD:F` &&
-	G=`git rev-parse --verify HEAD:A/G` &&
-	I=`git rev-parse --verify HEAD:A` &&
-	J=`git rev-parse --verify HEAD` &&
+	F=$(git rev-parse --verify HEAD:F) &&
+	G=$(git rev-parse --verify HEAD:A/G) &&
+	I=$(git rev-parse --verify HEAD:A) &&
+	J=$(git rev-parse --verify HEAD) &&
 	check_fsck &&
 
 	rm -f A/G &&
 	test_tick && git commit -a -m monkey &&
-	K=`git rev-parse --verify HEAD` &&
+	K=$(git rev-parse --verify HEAD) &&
 	check_fsck &&
 
 	check_have A B C D E F G H I J K L &&
-- 
2.3.3.GIT
Previous: Elia PintoNext: Elia Pinto
Message 4 of 12 in “use the $( ... ) construct for command substitution”
  1. 00/10 use the $( ... ) construct for command substitutionElia Pinto, Dec 22, 2015
  2. 01/10 t/t1100-commit-tree-options.sh: use the $( ... ) construct for command substitutionElia Pinto, Dec 22, 2015
  3. 02/10 t/t1401-symbolic-ref.sh: use the $( ... ) construct for command substitutionElia Pinto, Dec 22, 2015
  4. 03/10 t/t1410-reflog.sh: use the $( ... ) construct for command substitutionElia Pinto, Dec 22, 2015
  5. 04/10 t/t1511-rev-parse-caret.sh: use the $( ... ) construct for command substitutionElia Pinto, Dec 22, 2015
  6. 05/10 t/t1512-rev-parse-disambiguation.sh: use the $( ... ) construct for command substitutionElia Pinto, Dec 22, 2015
  7. 06/10 t/t1700-split-index.sh: use the $( ... ) construct for command substitutionElia Pinto, Dec 22, 2015
  8. 07/10 t/t2025-worktree-add.sh: use the $( ... ) construct for command substitutionElia Pinto, Dec 22, 2015
  9. 08/10 t/t2102-update-index-symlinks.sh: use the $( ... ) construct for command substitutionElia Pinto, Dec 22, 2015
  10. 09/10 t/t3030-merge-recursive.sh: use the $( ... ) construct for command substitutionElia Pinto, Dec 22, 2015
  11. 10/10 t/t3100-ls-tree-restrict.sh: use the $( ... ) construct for command substitutionElia Pinto, Dec 22, 2015
  12. Jonathan NiederDec 22, 2015

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.