From: "Kristoffer Haugsbakk" <kristofferhaugsbakk@fastmail•com>
To: "James Puleo" <james@jame•xyz>, git@vger•kernel.org
Subject: Re: git whatchanged: fatal: refusing to run without --i-still-use-this
Date: Fri, 19 Sep 2025 21:43:26 +0200 [thread overview]
Message-ID: <de3d58bd-5600-4bf3-812b-c329c4940afc@app.fastmail.com> (raw)
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 ;) )
next prev parent reply other threads:[~2025-09-19 19:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-19 19:24 git whatchanged: fatal: refusing to run without --i-still-use-this James Puleo
2025-09-19 19:43 ` Kristoffer Haugsbakk [this message]
[not found] ` <20250922000127.al45qxhhq4w3o27f@jame.xyz>
2025-09-22 7:30 ` Kristoffer Haugsbakk
2025-09-20 0:36 ` Ben Knoble
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=de3d58bd-5600-4bf3-812b-c329c4940afc@app.fastmail.com \
--to=kristofferhaugsbakk@fastmail$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=james@jame$(echo .)xyz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox