commit | fbf4bdfbf1ce543818363e7bc9286d73a61c0648 | [log] [tgz] |
---|---|---|
author | Junio C Hamano <gitster@pobox.com> | Wed Feb 10 14:20:07 2016 -0800 |
committer | Junio C Hamano <gitster@pobox.com> | Wed Feb 10 14:20:07 2016 -0800 |
tree | 3afd152f1da3c0cec7dd523b69fa1f00ef95b8b0 | |
parent | 0e35fcb412965f855e5ac6f469343e2f8e28d5ae [diff] | |
parent | f3ee9ca53bc04e9770747ea58951135d60b11a8d [diff] |
Merge branch 'ew/connect-verbose' There were a few "now I am doing this thing" progress messages in the TCP connection code that can be triggered by setting a verbose option internally in the code, but "git fetch -v" and friends never passed the verbose option down to that codepath. There was a brief discussion about the impact on the end-user experience by not limiting this to "fetch -v -v", but I think the conclusion is that this is OK to enable with a single "-v" as it is not too noisy. * ew/connect-verbose: pass transport verbosity down to git_connect