| commit | a5c98acec6ad8e8c397b1001621a4edfacc98516 | |
| author | Elia Pinto <gitter.spiros@gmail.com> | |
| Tue, 12 Jan 2016 11:49:29 +0000 (12 11:49 +0000) | ||
| committer | Junio C Hamano <gitster@pobox.com> | |
| Tue, 12 Jan 2016 19:49:46 +0000 (12 11:49 -0800) | ||
| tree | 04ada12c402723aef36c55174c80f4cfcbd588c7 | treesnapshot (tar.gz zip) |
| parent | 8c311f96a5a089d2f35654e9af7c44377a27839b | commitdiff |
t9130-git-svn-authors-file.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>
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/t9130-git-svn-authors-file.sh | diffblobblamehistory |