From: Elia Pinto Date: Thu, 07 Jan 2016 13:51:41 GMT Subject: [PATCH 01/10] t/t5900-repo-selection.sh: use the $( ... ) construct for command substitution Message-ID: <1452174710-28188-2-git-send-email-gitter.spiros@gmail.com> In-Reply-To: <1452174710-28188-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 --- t/t5900-repo-selection.sh | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/t/t5900-repo-selection.sh b/t/t5900-repo-selection.sh index 3d5b418..14e59c5 100755 --- a/t/t5900-repo-selection.sh +++ b/t/t5900-repo-selection.sh @@ -15,7 +15,7 @@ make_tree() { make_bare() { git init --bare "$1" && (cd "$1" && - tree=`git hash-object -w -t tree /dev/null` && + tree=$(git hash-object -w -t tree /dev/null) && commit=$(echo "$1" | git commit-tree $tree) && git update-ref HEAD $commit ) -- 2.3.3.GIT