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

Re: [PATCH 0/1] commit-graph: drop top-level --[no-]progress

From
Junio C Hamano <gitster@pobox.com>
Date
Sep 20, 2021, 21:24 UTC
Message-ID
<xmqqr1dj9c0b.fsf@gitster.g>
In-Reply-To
<cover.1631980949.git.me@ttaylorr.com>
Taylor Blau <me@ttaylorr.com> writes:
> An open question is whether the same should be done for the multi-pack-index
> command, whose top-level support for `--[no-]progress` was released in v2.32.0
> with 60ca94769c (builtin/multi-pack-index.c: split sub-commands, 2021-03-30).

We do not mind too much about "breaking backward compatibility" by removing the mistaken "git multi-pack-index --progress cmd", I would say. It's not like people would type it once every day and removing the "support" will break their finger-memory.

Previous: Taylor BlauNext: Taylor Blau
Message 5 of 10 in “commit-graph: drop top-level --[no-]progress”
  1. 0/1 commit-graph: drop top-level --[no-]progressTaylor Blau, Sep 18, 2021
  2. 1/1 builtin/commit-graph.c: don't accept common --[no-]progressTaylor Blau, Sep 18, 2021
  3. Derrick StoleeSep 20, 2021
  4. Taylor BlauSep 20, 2021
  5. Junio C HamanoSep 20, 2021
  6. Taylor BlauSep 20, 2021
  7. Ævar Arnfjörð BjarmasonSep 21, 2021
  8. Taylor BlauSep 21, 2021
  9. Junio C HamanoSep 22, 2021
  10. Jeff KingSep 21, 2021

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.