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

About global --progress option

From
Edmundo Carmona Antoranz <eantoranz@gmail.com>
Date
Nov 5, 2015, 03:13 UTC
Message-ID
<CAOc6etYiGV0v4gkkpudi3ACa6kA3H8CnqYYeSksfO4mGGfEyXg@mail.gmail.com>
Hi, everybody!

Coming back from my patch about the --[no-]progress option for checkout (it's already in next, J!!!!), I'd like to build into the idea of the single --[no-]progress option for git as a whole.

So, in order to know what/how things should be developed, let's start with a tiny survey

Which would be the correct development path?
- Two-step process: First step, implement global --[no-]progress at
the git level and also support the option from the builtins that
laready have it. Let it live like that for some releases (so that
people have the time to dump using the builtin option and start using
the global option) and then on the second step dump the builtin
options and keep the global one.
or
- A single step that would remove --[no-]progress from all builtins
that support it and would place it as a global git option?
Thanks in advance.
Next: Junio C Hamano
Message 1 of 4 in “About global --progress option”
  1. Edmundo Carmona AntoranzNov 5, 2015
  2. Junio C HamanoNov 5, 2015
  3. Edmundo Carmona AntoranzNov 5, 2015
  4. Jeff KingNov 5, 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.