threads / discuss / 64306

git whatchanged

Subject: git whatchanged

## tl;dr

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

replies: 1people: 2as markdown or json

Grzegorz Koperwas· Oct 13, 2025, 12:44 UTC · lore
Hello!
I recently got this output from git:
Show 6 quoted lines
> '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
I am letting you know, that I still use this command :)
Have a great day
Grzegorz Koperwas
Kristoffer Haugsbakk· Oct 13, 2025, 13:47 UTC · re: Grzegorz Koperwas · lore

Re: git whatchanged

On Mon, Oct 13, 2025, at 14:44, Grzegorz Koperwas wrote:
Show 10 quoted lines
> I recently got this output from git:
>
>> '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
>
> I am letting you know, that I still use this command :)

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

← back to recent threads