Re: Using command nominated for removal: whatchanged

From: Kristoffer Haugsbakk <kristofferhaugsbakk@fastmail.com>
Date: Sep 10, 2025, 13:53 UTC
Message-ID: <0908c4a2-f934-4f13-a25b-696803260ab3@app.fastmail.com>
In-Reply-To: <b32a369f-87c9-41f6-b1cb-81273945dc17@app.fastmail.com>

Hi Chirayu

Hi

On Wed, Sep 10, 2025, at 15:38, Chirayu Desai wrote:

Show 9 quoted lines

> Hello,
>
> Hope this email finds you well!
>
> 'git whatchanged' is nominated for removal.
>
> I still use this command. I usually run 'git whatchanged -1' and 'git
> whatchanged <commit>' to quickly see what files have changed in a
> particular commit.

You can replace it with `git log`:

• Given: `git whatchanged <opts>` • Replace with: `git log <opts> --no-merges --raw`

... with some minor output caveats about empty commits (commits with no changes).[1]

🔗 1: https://lore.kernel.org/git/20250825085428.GA367101@coredump.intra.peff.net/

> ... I usually run 'git whatchanged -1'

`git show --raw` should give a similar output. Although `git show` (with diff) or `git show --stat` are nicer in my opinion.

> I guess there might be some alias I could setup to achieve the same -
> it's more that this command has become a muscle memory at this point so
> I kept hitting the removal message, and here I am.

You can set up an alias, although not the exact alias `whatchanged` since core commands cannot be aliased (or shadowed I guess).

An alias like `watchanged` would work.

-- 
Kristoffer Haugsbakk