threads / discuss / 64925

Keep git whatchanged

Subject: Keep git whatchanged

## tl;dr

2 messages between Feb 5, 2026 and Feb 5, 2026.

replies: 1people: 2as markdown or json

Sam Berney· Feb 5, 2026, 10:59 UTC · lore
To whom it may concern,
I have no idea why anyone would want to remove `git whatchanged`. Can’t you count to see how many people use it or something? I’m going to keep using it till it stops working and then I’ll be grumpy. Don’t make me grumpy!
Sam Berney
Kristoffer Haugsbakk· Feb 5, 2026, 11:12 UTC · re: Sam Berney · lore

Re: Keep git whatchanged

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!

← back to recent threads