diff options
| author |  Elia Pinto <gitter.spiros@gmail.com> | 2016-01-07 14:51:46 +0100 |
|---|---|---|
| committer |  Junio C Hamano <gitster@pobox.com> | 2016-01-07 13:58:17 -0800 |
| commit | 7b8c0b53c320b03cb641f4e4c7b12049a36bd84e (patch) | |
| tree | f4cfd10d6d58d53f19d29d4e3f730d147700debf /pkt-line.c | |
| parent | t/t6032-merge-large-rename.sh: use the $( ... ) construct for command substit... (diff) | |
| download | tgif-7b8c0b53c320b03cb641f4e4c7b12049a36bd84e.tar.xz | |
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 'pkt-line.c')
0 files changed, 0 insertions, 0 deletions