Explicitly set push.default to matching to avoid the warning message; the test wants to verify there is no post-push report when --quiet is given, and this message interferes with it. This change is *iffy*, not in the sense that it breaks the test it touches, but because it is unclear if the output should be given when the user explicitly asked --quiet. On one hand, --quiet is a request to be "quiet", but on the other hand, this warning is meant to be shown in the face in large flashing red letters no matter what the user says, so... Signed-off-by: Junio C Hamano <gitster@xxxxxxxxx> --- t/t5541-http-push.sh | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/t/t5541-http-push.sh b/t/t5541-http-push.sh index 5b170be..07fa199 100755 --- a/t/t5541-http-push.sh +++ b/t/t5541-http-push.sh @@ -64,7 +64,10 @@ test_expect_success 'no empty path components' ' test_expect_success 'clone remote repository' ' rm -rf test_repo_clone && - git clone $HTTPD_URL/smart/test_repo.git test_repo_clone + git clone $HTTPD_URL/smart/test_repo.git test_repo_clone && + ( + cd test_repo_clone && git config push.default matching + ) ' test_expect_success 'push to remote repository (standard)' ' -- 1.7.10.475.g8b959 -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html