Skip to content

Commit cc301d7

Browse files
devzero2000gitster
authored andcommitted
contrib/examples/git-fetch.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> Reviewed-by: Jonathan Nieder <jrnieder@gmail.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
1 parent a22c9e8 commit cc301d7

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

contrib/examples/git-fetch.sh

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -146,13 +146,13 @@ esac
146146
reflist=$(get_remote_refs_for_fetch "$@")
147147
if test "$tags"
148148
then
149-
taglist=`IFS=' ' &&
149+
taglist=$(IFS=' ' &&
150150
echo "$ls_remote_result" |
151151
git show-ref --exclude-existing=refs/tags/ |
152152
while read sha1 name
153153
do
154154
echo ".${name}:${name}"
155-
done` || exit
155+
done) || exit
156156
if test "$#" -gt 1
157157
then
158158
# remote URL plus explicit refspecs; we need to merge them.

0 commit comments

Comments
 (0)