threads / discuss / 64237

git whatchanged

Subject: git whatchanged

## tl;dr

2 messages between Oct 2, 2025 and Oct 2, 2025.

replies: 1people: 2as markdown or json

Jiří Bašek· Oct 2, 2025, 06:48 UTC · lore

Hi, I am still using this very convenient command.

Best regards, Jiri Basek

> 'git whatchanged' is nominated for removal.

If you still use this command, please add an extra option, '--i-still-use-this', on the command line and let us know you still use it by sending an e-mail to <git@vger.kernel.org>. Thanks. fatal: refusing to run without --i-still-use-this

Kristoffer Haugsbakk· Oct 2, 2025, 07:12 UTC · re: Jiří Bašek · lore

Re: git whatchanged

Good morning
On Thu, Oct 2, 2025, at 08:48, Jiří Bašek wrote:
> I am still using this very convenient command.

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.

Here’s how you can replace your git-whatcanged(1) use with `git log`:

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

-- 
Stoffi

← back to recent threads