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

Re: git whatchanged

From
KHKristoffer Haugsbakk <kristofferhaugsbakk@fastmail.com>
Date
Nov 7, 2025, 13:11 UTC
Message-ID
<671d53bd-952f-4849-9e5e-910e49d4c4e4@app.fastmail.com>
In-Reply-To
<20251107124041.d6aac4345e89a9ac092c59e3@paxle.org>
On Fri, Nov 7, 2025, at 12:40, Franz Brauße wrote:
> I am using "git whatchanged" on a regular basis to understand what
> files specific commits touched and in what way.

This command is being removed because it was supplanted by git-log(1) a long while ago. Both commands use the same machinery, just with different defaults.

You can replace it with `git log` in this way:

• 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).

> I vote for not removing this functionality from git.

The intent behind the message was not to cast a vote but I can totally understand it being read that way.

See: https://git-scm.com/docs/BreakingChanges
-- 
Kristoffer Haugsbakk
Previous: Franz BraußeNext: Franz Brauße
Message 2 of 4 in “git whatchanged”
  1. Franz BraußeNov 7, 2025
  2. Kristoffer HaugsbakkNov 7, 2025
  3. Franz BraußeNov 7, 2025
  4. Kristoffer HaugsbakkNov 7, 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.