diff options
| author | Elia Pinto <gitter.spiros@gmail.com> | 2016-01-12 13:45:16 +0300 |
|---|---|---|
| committer | Junio C Hamano <gitster@pobox.com> | 2016-01-12 22:47:28 +0300 |
| commit | efa639fe6b850de699b675bf3e9c4b35f54f54bc (patch) | |
| tree | cb69a72ceb27892e9bcb31f1f9c6aab27345fc44 /t/t9110-git-svn-use-svm-props.sh | |
| parent | 1be2fa02b5ac97346e6745c767c559ee363ff378 (diff) | |
t9110-git-svn-use-svm-props.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/t9110-git-svn-use-svm-props.sh')
| -rwxr-xr-x | t/t9110-git-svn-use-svm-props.sh | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/t/t9110-git-svn-use-svm-props.sh b/t/t9110-git-svn-use-svm-props.sh index a06e4c5b8e..29fbdfdd3f 100755 --- a/t/t9110-git-svn-use-svm-props.sh +++ b/t/t9110-git-svn-use-svm-props.sh @@ -51,7 +51,7 @@ test_expect_success 'verify metadata for /dir' " test_expect_success 'find commit based on SVN revision number' " git svn find-rev r12 | - grep `git rev-parse HEAD` + grep $(git rev-parse HEAD) " test_expect_success 'empty rebase' " |