From: Jeff King <peff@peff.net>
To: Edmundo Carmona Antoranz <eantoranz@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 0/2] checkout: added two options to control progress output
Date: Thu, 29 Oct 2015 20:14:04 -0400 [thread overview]
Message-ID: <20151030001404.GB2123@sigill.intra.peff.net> (raw)
In-Reply-To: <CAOc6etakOy_zZ3fH_vS5UGGqouXTd7SJFtD6UC9bZRJaYWsRQw@mail.gmail.com>
On Thu, Oct 29, 2015 at 06:09:06PM -0600, Edmundo Carmona Antoranz wrote:
> A comment there: I think more builtins support --progress than the ones that
> support --no-progress, right?
Hopefully they are supported equally everywhere. Anybody using parseopt
should have something like (this is from builtin/clone.c):
OPT_BOOL(0, "progress", &option_progress,
N_("force progress reporting")),
That automatically gives us both --progress and --no-progress. And note
how option_progress is initialized to "-1" above that, so we know the
resulting value it stores will either be 1 (--progress),
0 (--no-progress), or -1 (no option specified).
-Peff
next prev parent reply other threads:[~2015-10-30 0:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-24 14:59 [PATCH 0/2] checkout: added two options to control progress output Edmundo Carmona
2015-10-29 22:05 ` Jeff King
2015-10-30 0:09 ` Edmundo Carmona Antoranz
2015-10-30 0:14 ` Jeff King [this message]
2015-10-30 16:52 ` 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=20151030001404.GB2123@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=eantoranz@gmail.com \
--cc=git@vger.kernel.org \
/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).