From: Jeff King <peff@peff.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: Avery Pennarun <apenwarr@gmail.com>, git@vger.kernel.org
Subject: Re: [PATCH v2] checkout: no progress messages if !isatty(2).
Date: Thu, 24 May 2012 14:34:57 -0400 [thread overview]
Message-ID: <20120524183457.GA11841@sigill.intra.peff.net> (raw)
In-Reply-To: <7vy5ohwhy7.fsf@alter.siamese.dyndns.org>
On Thu, May 24, 2012 at 11:29:52AM -0700, Junio C Hamano wrote:
> 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
next prev parent reply other threads:[~2012-05-24 18:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-24 5:18 [PATCH] progress: don't print if !isatty(2) Avery Pennarun
2012-05-24 5:45 ` Jeff King
2012-05-24 6:05 ` [PATCH] checkout: default to quiet " Avery Pennarun
2012-05-24 6:10 ` Jeff King
2012-05-24 6:12 ` [PATCH v2] checkout: no progress messages " Avery Pennarun
2012-05-24 18:29 ` Junio C Hamano
2012-05-24 18:34 ` Jeff King [this message]
2012-05-24 18:49 ` Avery Pennarun
2012-05-24 18:46 ` Avery Pennarun
2012-05-24 21:46 ` Junio C Hamano
2012-05-24 6:12 ` [PATCH] checkout: default to quiet " Avery Pennarun
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120524183457.GA11841@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=apenwarr@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).