diff options
| author | Junio C Hamano <gitster@pobox.com> | 2019-07-25 20:59:20 (GMT) |
|---|---|---|
| committer | Junio C Hamano <gitster@pobox.com> | 2019-07-25 20:59:20 (GMT) |
| commit | 023ff4cdf5793437313f481b4ef5b1ec247f2301 (patch) | |
| tree | fe222b4b3edeb442b7873d89d03556a1e11c1274 /po/README | |
| parent | 9c9b961d7eb15fb583a2a812088713a68a85f1c0 (diff) | |
| parent | 08a8ac88d868f3206e8faf0df2502ebc18925c33 (diff) | |
| download | git-023ff4cdf5793437313f481b4ef5b1ec247f2301.zip git-023ff4cdf5793437313f481b4ef5b1ec247f2301.tar.gz git-023ff4cdf5793437313f481b4ef5b1ec247f2301.tar.bz2 | |
Merge branch 'ab/test-env'
Many GIT_TEST_* environment variables control various aspects of
how our tests are run, but a few followed "non-empty is true, empty
or unset is false" while others followed the usual "there are a few
ways to spell true, like yes, on, etc., and also ways to spell
false, like no, off, etc." convention.
* ab/test-env:
env--helper: mark a file-local symbol as static
tests: make GIT_TEST_FAIL_PREREQS a boolean
tests: replace test_tristate with "git env--helper"
tests README: re-flow a previously changed paragraph
tests: make GIT_TEST_GETTEXT_POISON a boolean
t6040 test: stop using global "script" variable
config.c: refactor die_bad_number() to not call gettext() early
env--helper: new undocumented builtin wrapping git_env_*()
config tests: simplify include cycle test
Diffstat (limited to 'po/README')
| -rw-r--r-- | po/README | 2 |
1 files changed, 1 insertions, 1 deletions
@@ -293,7 +293,7 @@ To smoke out issues like these, Git tested with a translation mode that emits gibberish on every call to gettext. To use it run the test suite with it, e.g.: - cd t && GIT_TEST_GETTEXT_POISON=YesPlease prove -j 9 ./t[0-9]*.sh + cd t && GIT_TEST_GETTEXT_POISON=true prove -j 9 ./t[0-9]*.sh If tests break with it you should inspect them manually and see if what you're translating is sane, i.e. that you're not translating |