Re: [PATCH 8/8] trace: give repo_setup trace its own key
From: Junio C Hamano <hidden>
Date: 2016-06-15 22:50:40
Subsystem:
the rest · Maintainer:
Linus Torvalds
Possibly related (same subject, not in this thread)
- 2016-06-15 · [PATCH 8/8] trace: give repo_setup trace its own key · Jeff King <hidden>
- 2016-06-15 · Re: [PATCH 8/8] trace: give repo_setup trace its own key · Andreas Ericsson <hidden>
- 2016-06-15 · Re: [PATCH 8/8] trace: give repo_setup trace its own key · Jeff King <hidden>
- 2016-06-15 · Re: [PATCH 8/8] trace: give repo_setup trace its own key · Christian Couder <hidden>
- 2016-06-15 · Re: [PATCH 8/8] trace: give repo_setup trace its own key · Jonathan Nieder <hidden>
Jeff King [off-list ref] writes:
You no longer get this output with GIT_TRACE=1; instead, you can do GIT_TRACE_SETUP=1. Signed-off-by: Jeff King <redacted>
Hence you would need this on top? t/t1510-repo-setup.sh | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/t/t1510-repo-setup.sh b/t/t1510-repo-setup.sh
index 15101d5..ec50a9a 100755
--- a/t/t1510-repo-setup.sh
+++ b/t/t1510-repo-setup.sh@@ -57,7 +57,7 @@ test_repo () { export GIT_WORK_TREE fi && rm -f trace && - GIT_TRACE="$(pwd)/trace" git symbolic-ref HEAD >/dev/null && + GIT_TRACE_SETUP="$(pwd)/trace" git symbolic-ref HEAD >/dev/null && grep '^setup: ' trace >result && test_cmp expected result )