From: Ramkumar Ramachandra Date: Fri, 10 May 2013 14:29:38 GMT Subject: [PATCH 4/4] t4300 (rebase): don't unnecessarily set GIT_TRACE Message-ID: <1368196178-5807-5-git-send-email-artagnon@gmail.com> In-Reply-To: <1368196178-5807-1-git-send-email-artagnon@gmail.com> A couple of tests execute 'git rebase' with GIT_TRACE set to 1, but this trace output is not used anywhere. Remove it, since it is not relevant to what we are testing. Signed-off-by: Ramkumar Ramachandra --- t/t3400-rebase.sh | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/t/t3400-rebase.sh b/t/t3400-rebase.sh index 0841a12..d0d9442 100755 --- a/t/t3400-rebase.sh +++ b/t/t3400-rebase.sh @@ -137,13 +137,13 @@ test_expect_success 'rebase a single mode change' ' test_chmod +x A && test_tick && git commit -m modechange && - GIT_TRACE=1 git rebase master + git rebase master ' test_expect_success 'rebase is not broken by diff.renames' ' test_config diff.renames copies && git checkout filemove && - GIT_TRACE=1 git rebase force-3way + git rebase force-3way ' test_expect_success 'setup: recover' ' -- 1.8.3.rc1.52.gc14258d