| commit | cf60c8f346aff1a1e45b1c3fd2f8d3ab1483c275 | |
| author | Elia Pinto <gitter.spiros@gmail.com> | |
| Fri, 8 Jan 2016 11:06:24 +0000 (8 12:06 +0100) | ||
| committer | Junio C Hamano <gitster@pobox.com> | |
| Fri, 8 Jan 2016 20:54:06 +0000 (8 12:54 -0800) | ||
| tree | f9bf98970a2037efe04c23869cd2ee96c46e2c66 | treesnapshot (tar.gz zip) |
| parent | 0c923256a0116c2729a78dc01dfe223a67d7a95b | commitdiff |
t/t7602-merge-octopus-many.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/t7602-merge-octopus-many.sh | diffblobblamehistory |