* git whatchanged: fatal: refusing to run without --i-still-use-this
@ 2025-09-19 19:24 James Puleo
2025-09-19 19:43 ` Kristoffer Haugsbakk
2025-09-20 0:36 ` Ben Knoble
0 siblings, 2 replies; 4+ messages in thread
From: James Puleo @ 2025-09-19 19:24 UTC (permalink / raw)
To: git
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.
Thank you.
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: git whatchanged: fatal: refusing to run without --i-still-use-this
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
[not found] ` <20250922000127.al45qxhhq4w3o27f@jame.xyz>
2025-09-20 0:36 ` Ben Knoble
1 sibling, 1 reply; 4+ messages in thread
From: Kristoffer Haugsbakk @ 2025-09-19 19:43 UTC (permalink / raw)
To: James Puleo, git
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 ;) )
^ permalink raw reply [flat|nested] 4+ messages in thread* Re: git whatchanged: fatal: refusing to run without --i-still-use-this
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
@ 2025-09-20 0:36 ` Ben Knoble
1 sibling, 0 replies; 4+ messages in thread
From: Ben Knoble @ 2025-09-20 0:36 UTC (permalink / raw)
To: James Puleo; +Cc: git
> Le 19 sept. 2025 à 16:00, James Puleo <james@jame•xyz> a écrit :
>
> 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.
In that case:
git log -- path/to/deleted/file
(or rev-list?) would get you there quickly.
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2025-09-22 7:30 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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
[not found] ` <20250922000127.al45qxhhq4w3o27f@jame.xyz>
2025-09-22 7:30 ` Kristoffer Haugsbakk
2025-09-20 0:36 ` Ben Knoble
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox