summaryrefslogtreecommitdiff
path: root/contrib/remote-helpers/test-hg-bidi.sh
diff options
context:
space:
mode:
authorLibravatar Jeff King <peff@peff.net>2013-09-18 16:06:50 -0400
committerLibravatar Junio C Hamano <gitster@pobox.com>2013-09-18 13:34:46 -0700
commit2856cbf0ae604c233e7dc62ba7931a469165ce4f (patch)
tree212d7f1362f9a939b8c429292adcfbf727254cf6 /contrib/remote-helpers/test-hg-bidi.sh
parentclone: send diagnostic messages to stderr (diff)
downloadtgif-2856cbf0ae604c233e7dc62ba7931a469165ce4f.tar.xz
clone: treat "checking connectivity" like other progress
When stderr does not point to a tty, we typically suppress "we are now in this phase" progress reporting (e.g., we ask the server not to send us "counting objects" and the like). The new "checking connectivity" message is in the same vein, and should be suppressed. Since clone relies on the transport code to make the decision, we can simply sneak a peek at the "progress" field of the transport struct. That properly takes into account both the verbosity and progress options we were given, as well as the result of isatty(). Note that we do not set up that progress flag for a local clone, as we do not fetch using the transport at all. That's acceptable here, though, because we also do not perform a connectivity check in that case. Signed-off-by: Jeff King <peff@peff.net> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'contrib/remote-helpers/test-hg-bidi.sh')
0 files changed, 0 insertions, 0 deletions