summaryrefslogtreecommitdiff
path: root/t/t6132-pathspec-exclude.sh
diff options
context:
space:
mode:
authorElia Pinto <gitter.spiros@gmail.com>2016-01-07 13:51:46 (GMT)
committerJunio C Hamano <gitster@pobox.com>2016-01-07 21:58:17 (GMT)
commit7b8c0b53c320b03cb641f4e4c7b12049a36bd84e (patch)
treef4cfd10d6d58d53f19d29d4e3f730d147700debf /t/t6132-pathspec-exclude.sh
parent59f9c6c3cd308342ecf814a2a7636a9395c40e49 (diff)
downloadgit-7b8c0b53c320b03cb641f4e4c7b12049a36bd84e.zip
git-7b8c0b53c320b03cb641f4e4c7b12049a36bd84e.tar.gz
git-7b8c0b53c320b03cb641f4e4c7b12049a36bd84e.tar.bz2
t/t6132-pathspec-exclude.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>
Diffstat (limited to 't/t6132-pathspec-exclude.sh')
-rwxr-xr-xt/t6132-pathspec-exclude.sh2
1 files changed, 1 insertions, 1 deletions
diff --git a/t/t6132-pathspec-exclude.sh b/t/t6132-pathspec-exclude.sh
index e1e1b1f..d51595c 100755
--- a/t/t6132-pathspec-exclude.sh
+++ b/t/t6132-pathspec-exclude.sh
@@ -7,7 +7,7 @@ test_description='test case exclude pathspec'
test_expect_success 'setup' '
for p in file sub/file sub/sub/file sub/file2 sub/sub/sub/file sub2/file; do
if echo $p | grep /; then
- mkdir -p `dirname $p`
+ mkdir -p $(dirname $p)
fi &&
: >$p &&
git add $p &&