]> git.ipfire.org Git - thirdparty/git.git/commit - t/t9137-git-svn-dcommit-clobber-series.sh
t9137-git-svn-dcommit-clobber-series.sh: use the $( ... ) construct for command subst...
authorElia Pinto <gitter.spiros@gmail.com>
Tue, 12 Jan 2016 11:49:31 +0000 (11:49 +0000)
committerJunio C Hamano <gitster@pobox.com>
Tue, 12 Jan 2016 19:49:47 +0000 (11:49 -0800)
commit2525c5170f1088dac0aeb18444041f9fff04761a
treef7eba049d353a8715775a48f705a99f057b24243
parentbecd67fd281fa0efdf8f6346f311954a237dc991
t9137-git-svn-dcommit-clobber-series.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>
t/t9137-git-svn-dcommit-clobber-series.sh