Re: [PATCH] git-update-index: report(...) now flushes stdout after printing the report line

From: Junio C Hamano <gitster@pobox.com>
Date: Jan 6, 2010, 01:04 UTC
Message-ID: <7vwrzwoxh4.fsf@alter.siamese.dyndns.org>
In-Reply-To: <be6fef0d1001031503h11cb65c6ha34eee345b9b7055@mail.gmail.com>

Tay Ray Chuan <rctay89@gmail.com> writes:

Show 10 quoted lines

> from your above message solely and setting aside your original patch,
> I presume that you want to introduce the ability to force progress
> reporting even if stderr isn't a terminal.
>
> I am working a feature (display progress for http operations) that
> happens to add this ability to git-push and git-fetch, by specifying
> the --progress option.
>
> Regarding git-pull - I guess it's only git-fetch (being
> transport-related) that reports progress?

Are you talking about this topic?

 * tc/clone-v-progress (2009-12-26) 4 commits
  - clone: use --progress to force progress reporting
  - clone: set transport->verbose when -v/--verbose is used
  - git-clone.txt: reword description of progress behaviour
  - check stderr with isatty() instead of stdout when deciding to show progress

What do people think about it? I vaguely recall that somebody asked to add a warning to release notes on the behaviour change to this series, and I think it may be a worthwhile thing to do (e.g. "Earlier we did X but now we do Y; change things in this way if you want us to keep doing X"), but otherwise I think it is a sensible change.