Re: [PATCH v2] checkout: no progress messages if !isatty(2).
- From
Jeff King <peff@peff.net>
- Date
- May 24, 2012, 18:34 UTC
- Message-ID
- <20120524183457.GA11841@sigill.intra.peff.net>
- In-Reply-To
- <7vy5ohwhy7.fsf@alter.siamese.dyndns.org>
On Thu, May 24, 2012 at 11:29:52AM -0700, Junio C Hamano wrote:
Show 7 quoted lines
> I do not seem to find a sane justification for > > git $cmd --progress 2>output > > use case and I do not immediately see how that "output" file can be > useful. But we've allowed it for a long time, so probably this version is > safer. Besides, it is more explicit.
Actually, I ran across a case of this just recently. If you are writing a graphical interface that wraps git, scraping "--progress" output from a pipe is the only way you can provide a progress meter within your interface. That is what the "GitHub for {Mac,Windows}" interfaces do (they also use libgit2 where possible, but it is far from feature complete).
-Peff