From: Kristoffer Haugsbakk <kristofferhaugsbakk@fastmail.com>
Date: Tue, 03 Mar 2026 16:45:32 GMT
Subject: Re: git whatchanged --i-still-use-it
Message-ID: <9595d154-8586-4afd-ac1a-f5c133e10f9b@app.fastmail.com>
In-Reply-To: <bhYbjxeZY0QZt48g6XVTVfyPo6vbv9yeYLsw9PgFdVKgye6Ue0cAPy_RkNTwAOYEANhHyD6QbaxZrWaPS4__jlTcAVKOaEjrDgAxQYKdYvE=@protonmail.com>

Good evening

On Tue, Mar 3, 2026, at 17:01, Antoine Cousson wrote:
> I would like to say that I still use `git whatchanged` I like the way
> we see the modified files instead of just `git log`

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.

> And actually I never saw the message before today when I showed the
> command to a friend of mine, will it be removed soon ?

It is planned for removal in Git 3.0. There is no plan for when Git 3.0
will be released.

See: https://git-scm.com/docs/BreakingChanges

> Is there any alternatives that are straight to the point without any
> args or something?

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

You can also use `--patch` to see the full diffs.

>
> In any cases, thanks for your amazing work,
>[snip]