From: Stephen Boyd <bebarino@gmail.com>
To: "Nguyễn Thái Ngọc Duy" <pclouds@gmail.com>
Cc: git@vger.kernel.org, Junio C Hamano <gitster@pobox.com>,
Jeff King <peff@peff.net>
Subject: Re: [PATCH] fsck: print progress
Date: Sat, 05 Nov 2011 00:53:20 -0700 [thread overview]
Message-ID: <4EB4EB70.40801@gmail.com> (raw)
In-Reply-To: <1320376242-27851-1-git-send-email-pclouds@gmail.com>
On 11/03/2011 08:10 PM, Nguyễn Thái Ngọc Duy wrote:
> diff --git a/Documentation/git-fsck.txt b/Documentation/git-fsck.txt
[...]
> +--progress::
> +--no-progress::
> + When fsck is run in a terminal, it will show the progress.
> + These options can force progress to be shown or not
> + regardless terminal check.
Can we reuse the --progress description in fetch-options.txt (minus the q)?
--[no]-progress::
Progress status is reported on the standard error stream
by default when it is attached to a terminal. This flag
forces progress status even if the standard error stream
is not directed to a terminal.
> ++
> +Progress is not shown when --verbose is used. --progress is ignored
> +in this case.
What progress isn't shown? How about
If --verbose is used with --progress the progress status
will not be shown.
next prev parent reply other threads:[~2011-11-05 7:57 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-02 12:06 long fsck time Nguyen Thai Ngoc Duy
2011-11-02 12:10 ` Nguyen Thai Ngoc Duy
2011-11-02 21:33 ` Jeff King
2011-11-03 1:36 ` Nguyen Thai Ngoc Duy
2011-11-03 3:21 ` [PATCH] fsck: print progress Nguyễn Thái Ngọc Duy
2011-11-03 3:33 ` Jeff King
2011-11-03 8:50 ` Nguyễn Thái Ngọc Duy
2011-11-03 19:38 ` Jeff King
2011-11-03 19:43 ` Junio C Hamano
2011-11-03 19:51 ` Jeff King
2011-11-03 20:28 ` Junio C Hamano
2011-11-03 20:29 ` Jeff King
2011-11-03 20:56 ` Junio C Hamano
2011-11-03 21:18 ` Jeff King
2011-11-04 3:10 ` Nguyễn Thái Ngọc Duy
2011-11-05 7:53 ` Stephen Boyd [this message]
2011-11-05 9:02 ` Nguyen Thai Ngoc Duy
2011-11-05 19:15 ` Stephen Boyd
2011-11-05 23:59 ` Junio C Hamano
2011-11-06 2:37 ` Nguyen Thai Ngoc Duy
2011-11-06 6:05 ` Junio C Hamano
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4EB4EB70.40801@gmail.com \
--to=bebarino@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=pclouds@gmail.com \
--cc=peff@peff.net \
/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.
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 NNTP newsgroup(s).