The Git CodingGuidelines prefer the $( ... ) construct for command substitution instead of using the back-quotes, or grave accents (`..`).
The backquoted form is the historical 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. Because of this the POSIX shell adopted the $(…) feature from the Korn shell. Signed-off-by: Elia Pinto <gitter.spi...@gmail.com> --- t/t0204-gettext-reencode-sanity.sh | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/t/t0204-gettext-reencode-sanity.sh b/t/t0204-gettext-reencode-sanity.sh index 8437e51..fc9f21e 100755 --- a/t/t0204-gettext-reencode-sanity.sh +++ b/t/t0204-gettext-reencode-sanity.sh @@ -58,7 +58,7 @@ test_expect_success GETTEXT_LOCALE 'gettext: Fetching a UTF-8 msgid -> UTF-8' ' # How these quotes get transliterated depends on the gettext implementation: # # Debian: ,einfaldar' og ,,tvöfaldar" [GNU libintl] -# FreeBSD: `einfaldar` og "tvöfaldar" [GNU libintl] +# FreeBSD: $(einfaldar) og "tvöfaldar" [GNU libintl] # Solaris: ?einfaldar? og ?tvöfaldar? [Solaris libintl] # # Just make sure the contents are transliterated, and don't use grep -q -- 1.7.10.4 -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
