unimplemented.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>
Elia Pinto committed
Dec 22, 2015 at 15:10 UTC
92bea9530ba2a69cc0f0e3a3d67e60fafb2444d9
1 file changed
+1
-1
unimplemented.sh
+1
-1
@@ -1,4 +1,4 @@
1
#!/bin/sh
2
3
-echo >&2 "fatal: git was built without support for `basename $0` (@@REASON@@)."
3
+echo >&2 "fatal: git was built without support for $(basename $0) (@@REASON@@)."
4
exit 128