From: Kristoffer Haugsbakk <kristofferhaugsbakk@fastmail.com>
Date: Fri, 19 Sep 2025 19:43:26 GMT
Subject: Re: git whatchanged: fatal: refusing to run without --i-still-use-this
Message-ID: <de3d58bd-5600-4bf3-812b-c329c4940afc@app.fastmail.com>
In-Reply-To: <d94afaec66f8ab8058764cee08e9dd56435dd667.camel@jame.xyz>

Hi 
On Fri, Sep 19, 2025, at 21:24, James Puleo wrote:
> Hello World,
>
> I have git version 2.51.0. I encountered today entirely on my own this
> fatal: refusing to run without --i-still-use-this
>
> Why I was using this command: There is a bit of code I wrote in a file
> since deleted (from the tree). I knew the path but not whichever ref
> last had the file I was looking for.
>
> Having a file listing consisting of purely the file paths that have
> changed seems like a useful tool, that's all. If this isn't fueled by a
> technical challenge, I don't see a reason to make simple things have a
> difficult path.

This command is getting removed 
because it's been replaced by git-log.
git-log can do evereything git-whatchanged
can do and has better defaults "for humans".
For example: --stat or --name-only which gives
files-changed output without technical details
like (I guess) filemode.

But you can keep the whatchanged behavior with

    git log --raw --no-merges

-- 
(sent from mobile—check option names
for me ;) )