summaryrefslogtreecommitdiff
path: root/git-gui/lib/themed.tcl
diff options
context:
space:
mode:
authorLibravatar Johannes Schindelin <johannes.schindelin@gmx.de>2016-03-23 11:55:07 +0100
committerLibravatar Junio C Hamano <gitster@pobox.com>2016-03-23 09:59:21 -0700
commit2ec20212c56575dc5e6875f36fa68b6b4a8edd70 (patch)
tree21ff998e69f130f84b47c9a3feaf2e6f2bb23955 /git-gui/lib/themed.tcl
parentconfig --show-origin: report paths with forward slashes (diff)
downloadtgif-2ec20212c56575dc5e6875f36fa68b6b4a8edd70.tar.xz
t1300-repo-config: make it resilient to being run via 'sh -x'
One way to diagnose broken regression tests is to run the test script using 'sh -x t... -i -v' to find out which call actually demonstrates the symptom. Hence it is pretty counterproductive if the test script behaves differently when being run via 'sh -x', in particular when using test_cmp or test_i18ncmp on redirected stderr. A more recent way "sh tXXXX -i -v -x" has the same issue. So let's use test_i18ngrep (as suggested by Jonathan Nieder) instead of test_cmp/test_i18ncmp to verify that stderr looks as expected. Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'git-gui/lib/themed.tcl')
0 files changed, 0 insertions, 0 deletions