git whatchanged -- yes, I still use this

Jeffery Carr· Oct 5, 2025, 02:14 UTC · lore

If you are going to remove it, "alias" it to something.

alternatively, I guess I'll make "git-whatchanged" binary to do it.

Can I ask what the problem is with it? The code is a mess I'm guessing.

I'd also suggest, instead of the message:

'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

add to the message:

<run this instead>

love & respect, jcarr

Kristoffer Haugsbakk· Oct 5, 2025, 10:31 UTC · re: Jeffery Carr · lore

Re: git whatchanged -- yes, I still use this

On Sun, Oct 5, 2025, at 04:14, Jeffery Carr wrote:

> If you are going to remove it, "alias" it to something.

Git doesn’t have built-in aliases, if you mean Git aliases more literally. If not then it already acts as a sort of alias, I guess.

> alternatively, I guess I'll make "git-whatchanged" binary to do it.

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 to replace it with git-log(1):

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

Show 6 quoted lines

> I'd also suggest, instead of the message:
>
>[snip]
> add to the message:
>
> <run this instead>

This is coming in the next versions.