git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH 0/2] checkout: added two options to control progress output

From
Jeff King <peff@peff.net>
Date
Oct 30, 2015, 00:14 UTC
Message-ID
<20151030001404.GB2123@sigill.intra.peff.net>
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
Previous: Edmundo Carmona AntoranzNext: Junio C Hamano
Message 4 of 5 in “checkout: added two options to control progress output”
  1. 0/2 checkout: added two options to control progress outputEdmundo Carmona, Oct 24, 2015
  2. Jeff KingOct 29, 2015
  3. Edmundo Carmona AntoranzOct 30, 2015
  4. Jeff KingOct 30, 2015
  5. Junio C HamanoOct 30, 2015

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.