'git whatchanged' is nominated for removal. If you still use this command, please add an extra option, '--i-still-use-this', on the command line and let us know you still use it by sending an e-mail to <git@vger.kernel.org>. Thanks. fatal: refusing to run without --i-still-use-thi
;) I still use this one.
with kind regards, Remke Schuurmans The Netherlands
Re: git whatchanged
On Fri, Oct 31, 2025, at 09:02, Remke Schuurmans wrote:
> 'git whatchanged' is nominated for removal. > If you still use this command, please add an extra > option, '--i-still-use-this', on the command line > and let us know you still use it by sending an e-mail > to <git@vger.kernel.org>. Thanks. > fatal: refusing to run without --i-still-use-thi > > ;) I still use this one.
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.
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).
Re: git whatchanged
On Fri, Oct 31, 2025, at 10:02, Remke Schuurmans wrote:
> Thank you for taking time to answer my mail. > I had this command still as an alias :)) > > I'm old scool :)
You cannot alias builtin Git commands on the version you are running (which must be Git 2.51.0 given the output you got).
But you can alias builtin commands that are deprecated on Git 2.51.1 and 2.51.2:
git config set --global alias.whatchanged 'log --raw --no-merges'