git-gui/po/glossary/ 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")
	perl -i -pe 'BEGIN{undef $/;} s/`(.+?)`/\$(\1)/smg'  "${_f}"

and then carefully proof-read.

Signed-off-by: Elia Pinto <>
Reviewed-by: Jonathan Nieder <>
Signed-off-by: Junio C Hamano <>
This commit is contained in:
Elia Pinto 2015-12-22 15:10:29 +01:00 committed by Junio C Hamano
parent 57eb1bef7d
commit 4796af1510
1 changed files with 2 additions and 2 deletions

View File

@ -11,7 +11,7 @@
if [ $# -eq 0 ]
cat <<!
Usage: `basename $0` git-gui-glossary.txt > git-gui-glossary.pot
Usage: $(basename $0) git-gui-glossary.txt > git-gui-glossary.pot
exit 1;
@ -33,7 +33,7 @@ cat <<!
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"POT-Creation-Date: `date +'%Y-%m-%d %H:%M%z'`\n"
"POT-Creation-Date: $(date +'%Y-%m-%d %H:%M%z')\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <>\n"