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

Re: [PATCH v3 4/5] builtin/pack-redundant: remove subcommand with breaking changes

From
Junio C Hamano <gitster@pobox.com>
Date
Jan 21, 2025, 21:09 UTC
Message-ID
<xmqqed0vzxep.fsf@gitster.g>
In-Reply-To
<20250120-pks-remote-branches-deprecation-v3-4-c7e539b6a84f@pks.im>
Patrick Steinhardt <ps@pks.im> writes:
> The git-pack-redundant(1) subcommand has been announced for removal with
> 53a92c9552 (Documentation/BreakingChanges: announce removal of
> git-pack-redundant(1), 2024-09-02). Stop compiling the subcommand in
> case the `WITH_BREAKING_CHANGES` build flag is set.
Nice.

The date it was added to BreakingChanges document is probably of much lessor impact and importance to the end users than when we stopped working unless the user gave "--i-still-use-this" which was done by 4406522b (pack-redundant: escalate deprecation warning to an error, 2023-03-23) that was in Git 2.41.

Other than that, I love this step. The fewer the subcommands, the happier the users ;-)

Previous: Patrick SteinhardtNext: Patrick Steinhardt
Message 6 of 10 in “remote: announce removal of "branches/" and "remotes/"”
  1. 0/5 remote: announce removal of "branches/" and "remotes/"Patrick Steinhardt, Jan 20, 2025
  2. 1/5 Makefile: wire up build option for deprecated featuresPatrick Steinhardt, Jan 20, 2025
  3. 2/5 ci: merge linux-gcc-default into linux-gccPatrick Steinhardt, Jan 20, 2025
  4. 3/5 ci: repurpose "linux-gcc" job for deprecationsPatrick Steinhardt, Jan 20, 2025
  5. 4/5 builtin/pack-redundant: remove subcommand with breaking changesPatrick Steinhardt, Jan 20, 2025
  6. Junio C HamanoJan 21, 2025
  7. 5/5 remote: announce removal of "branches/" and "remotes/"Patrick Steinhardt, Jan 20, 2025
  8. Junio C HamanoJan 21, 2025
  9. Patrick SteinhardtJan 22, 2025
  10. Junio C HamanoJan 22, 2025

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.