push/fetch/clone --no-progress suppresses progress output
authorClemens Buchacher <drizzd@aon.at>
Mon, 13 Feb 2012 20:17:15 +0000 (21:17 +0100)
committerJunio C Hamano <gitster@pobox.com>
Mon, 13 Feb 2012 21:06:53 +0000 (13:06 -0800)
commit01fdc21f6e90f56fc5a49cbba751d9ead19b2f03
tree7a8503c31417735d5765ddd1c2a63749e254d513
parent58d4203aa617293d1dc3746a1ea33d84eb766e0f
push/fetch/clone --no-progress suppresses progress output

By default, progress output is disabled if stderr is not a terminal.
The --progress option can be used to force progress output anyways.
Conversely, --no-progress does not force progress output. In particular,
if stderr is a terminal, progress output is enabled.

This is unintuitive. Change --no-progress to force output off.

Signed-off-by: Clemens Buchacher <drizzd@aon.at>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
builtin/clone.c
builtin/fetch-pack.c
builtin/fetch.c
builtin/push.c
builtin/send-pack.c
t/t5523-push-upstream.sh
transport.c