Tay Ray Chuan <rctay89@xxxxxxxxx> 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 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. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html