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

Re: Keep git whatchanged

From
KHKristoffer Haugsbakk <kristofferhaugsbakk@fastmail.com>
Date
Feb 5, 2026, 11:12 UTC
Message-ID
<1e8924cd-9e23-4fc5-b25f-9683da917b43@app.fastmail.com>
In-Reply-To
<106C80F0-C92E-4F23-9CCA-631AFF12AC65@samuelberney.com>
On Thu, Feb 5, 2026, at 11:59, Sam Berney wrote:
> I have no idea why anyone would want to remove `git whatchanged`.

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

> Can’t you count to see how many people use it or something?
git(1) doesn’t have telemetry. Sending an email here is the telemtry. :)
> I’m going to keep using it till it stops working and then I’ll be
> grumpy. Don’t make me grumpy!
Previous: Sam Berney
Message 2 of 2 in “Keep git whatchanged”
  1. Sam BerneyFeb 5, 2026
  2. Kristoffer HaugsbakkFeb 5, 2026

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.