Hi, (you dropped the Cc list; fixed that for you.) On Sun, Jan 3, 2010 at 6:41 PM, Sebastian Thiel <byronimo@xxxxxxxxx> wrote: > Adding a commandline option to git-push and git-pull that enforces progress > messages to be printed to stderr would be a feasible and simple fix that would > clearly improve the usability of tortoise-git and git-python to name only two. > > That said, I hope I managed to make myself clear enough this time to help the > people in charge to figure out how to solve the issue. Once the desired solution > has been sketched out and the desired new commandline options have been named, > it could even be me to implement it if necessary, as I'd consider it a gentle > start into the world of the git codebase. 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? -- Cheers, Ray Chuan -- 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