# git whatchanged 2 messages from 2025-08-26 to 2025-08-26. Participants: Chris Palmer, Kristoffer Haugsbakk. Thread: https://gitlist.dev/t/64036 ## Chris Palmer, 2025-08-26 13:04 Subject: git whatchanged Message-ID: <1011073f-9930-4360-a42f-71eb7421fe3f@chrispalmer.uk> URL: https://gitlist.dev/e/1011073f-9930-4360-a42f-71eb7421fe3f%40chrispalmer.uk ``` 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 ``` ## Kristoffer Haugsbakk, 2025-08-26 13:54 Subject: Re: git whatchanged Message-ID: <04d5ce4f-53aa-465a-aeb1-bef84532e424@app.fastmail.com> URL: https://gitlist.dev/e/04d5ce4f-53aa-465a-aeb1-bef84532e424%40app.fastmail.com In-Reply-To: <1011073f-9930-4360-a42f-71eb7421fe3f@chrispalmer.uk> ``` 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 ` • Replace with: `git log --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 ```