We still use whatchanged frequently. Sometimes to check the later commits, and sometimes as an easy way of searching for changes to a specific file.
I'm not clear whether you are proposing removing the functionality altogether, or whether there is a new/better way to do it.
Thanks, Chris
-- Chris Palmer chris@chrispalmer.uk
Re: git whatchanged
Hi
On Tue, Aug 26, 2025, at 15:04, Chris Palmer wrote:
> We still use whatchanged frequently. Sometimes to check the later > commits, and sometimes as an easy way of searching for changes to a > specific file. > > I'm not clear whether you are proposing removing the functionality > altogether, or whether there is a new/better way to do it.
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'm not clear whether you are proposing removing the functionality > altogether,
Yes, the command is slated for removal in Git 3.0. They have not decided when that version will be released.
(although the functionality is still covered by git-log(1))
See this doc (from 2.51.0): https://github.com/git/git/tree/c44beea485f0f2feaf460e2ac87fdd5608d63cf0/Documentation/BreakingChanges.adoc
-- Kristoffer Haugsbakk