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

Re: Git whatchanged

From
KHKristoffer Haugsbakk <kristofferhaugsbakk@fastmail.com>
Date
Oct 8, 2025, 14:42 UTC
Message-ID
<d1273222-df3d-4e1d-ab20-1a49f1a692bd@app.fastmail.com>
In-Reply-To
<GV2P251MB09937AD11689D3148CD342D8F8E1A@GV2P251MB0993.EURP251.PROD.OUTLOOK.COM>
Good evening
On Wed, Oct 8, 2025, at 16:20, Filippo Falezza wrote:
> I am reaching out as I am still using the whatchanged option in git,
> which is very useful for my coding and handling merges.
> Please keep this option and do not break userspace.

This command is being removed because git-log(1) supplanted it over 12 years ago. Both commands use the same machinery, just with different defaults.

You can replace the command with `git log` thus:

• Given: `git whatchanged <opts>` • Replace with: `git log <opts> --no-merges --raw`

Additionally for the sake of readability, you might have more use for `--stat` or `--name-only` rather than `--raw` if you are only reading the output (not feeding the output to another program).

Previous: Filippo Falezza
Message 2 of 2 in “Git whatchanged”
  1. Filippo FalezzaOct 8, 2025
  2. Kristoffer HaugsbakkOct 8, 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.