From: Elia Pinto <gitter.spiros@gmail.com>
Date: Wed, 23 Dec 2015 13:45:53 +0000 (+0100)
Subject: t/t5505-remote.sh: use the $( ... ) construct for command substitution
X-Git-Tag: v2.8.0-rc0~103^2~56
X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=c00978144a523854171aa9ef2857dc16c08d34d4;p=thirdparty%2Fgit.git

t/t5505-remote.sh: use the $( ... ) construct for command substitution

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>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
---

diff --git a/t/t5505-remote.sh b/t/t5505-remote.sh
index dfaf9d9f68..1a8e3b81c8 100755
--- a/t/t5505-remote.sh
+++ b/t/t5505-remote.sh
@@ -85,7 +85,7 @@ test_expect_success C_LOCALE_OUTPUT 'check remote-tracking' '
 test_expect_success 'remote forces tracking branches' '
 	(
 		cd test &&
-		case `git config remote.second.fetch` in
+		case $(git config remote.second.fetch) in
 		+*) true ;;
 		 *) false ;;
 		esac