summaryrefslogtreecommitdiff
path: root/t/t9132-git-svn-broken-symlink.sh
diff options
context:
space:
mode:
authorJunio C Hamano <gitster@pobox.com>2016-02-10 22:20:07 (GMT)
committerJunio C Hamano <gitster@pobox.com>2016-02-10 22:20:07 (GMT)
commitfbf4bdfbf1ce543818363e7bc9286d73a61c0648 (patch)
tree3afd152f1da3c0cec7dd523b69fa1f00ef95b8b0 /t/t9132-git-svn-broken-symlink.sh
parent0e35fcb412965f855e5ac6f469343e2f8e28d5ae (diff)
parentf3ee9ca53bc04e9770747ea58951135d60b11a8d (diff)
downloadgit-fbf4bdfbf1ce543818363e7bc9286d73a61c0648.zip
git-fbf4bdfbf1ce543818363e7bc9286d73a61c0648.tar.gz
git-fbf4bdfbf1ce543818363e7bc9286d73a61c0648.tar.bz2
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
Diffstat (limited to 't/t9132-git-svn-broken-symlink.sh')
0 files changed, 0 insertions, 0 deletions