From: Tay Ray Chuan Date: Wed, 06 Jan 2010 01:51:06 GMT Subject: Re: [PATCH] git-update-index: report(...) now flushes stdout after printing the report line Message-ID: In-Reply-To: <7vwrzwoxh4.fsf@alter.siamese.dyndns.org> Hi, On Wed, Jan 6, 2010 at 9:04 AM, Junio C Hamano wrote: > Tay Ray Chuan writes: > >> 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 no, I'm not referring to that - the topic I mentioned is still off-list. > 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. Yes, that request was from Dscho, and Miklos said something to that effect as well. Could you advise how one could go about adding such a warning, as I'm not sure about the release schedule details. -- Cheers, Ray Chuan