Re: [PATCH v2 0/2] Nominating "whatchanged" for removal

From: Patrick Steinhardt <ps@pks.im>
Date: May 2, 2025, 09:08 UTC
Message-ID: <aBSLejDoqomUO3xE@pks.im>
In-Reply-To: <20250501225958.2947677-1-gitster@pobox.com>

On Thu, May 01, 2025 at 03:59:56PM -0700, Junio C Hamano wrote:

> This does not go far enough to touch the "Git 3.0 removal" list in
> Documentation/BreakingChanges.adoc, but is a preparatory step
> necessary if we ever wanted to do so in the future.

I'm a little confused. These patches very much feel like starting the deprecation process for git-whatchanged(1), so why wouldn't we at the same time list it as an upcoming breaking change? Or is the intent rather to figure out whether anybody is still using this command so that we can then deprecate it after a couple releases if we haven't heard back from anybody?

Patrick

$ 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.