{"thread":{"id":"65499","subject":"I still heavily use git whatchanged after more than 10 years","startedAt":"2026-04-16T17:06:52Z","lastAt":"2026-04-16T17:18:04Z","messageCount":2,"participants":["Chester","Junio C Hamano"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"541757","messageId":"CAHvvhRS9VJgyAdivR6J1Hz14jSuBJOj8Bpdu+g4fV45LRSeS8A@mail.gmail.com","threadId":"65499","inReplyTo":null,"subject":"I still heavily use git whatchanged after more than 10 years","fromName":"Chester","fromEmail":"just13.0818@gmail.com","sentAt":"2026-04-16T17:06:40Z","receivedAt":"2026-04-16T17:06:52Z","isPatch":false,"body":"Dear Git developers,\n\nI saw the message that git whatchanged is now nominated for removal\nand requires the --i-still-use-this flag.\n\nI want to let you know that I have been using git whatchanged for more\nthan ten years, and I still use it very frequently in my daily\nworkflow.\n\nIt has become a muscle-memory command for me, and I find the\ncombination of showing the log with raw diffs (while skipping merges\nby default) very convenient.\n\nI understand that it can be replaced with git log --raw --no-merges,\nbut after so many years, git whatchanged just feels more natural and\nquicker to type for my use case.\n\nThank you for maintaining Git and for reaching out to users before\nremoving long-standing commands.\n\nBest regards,\nChester\n"},{"id":"541758","messageId":"xmqqtsta259z.fsf@gitster.g","threadId":"65499","inReplyTo":"CAHvvhRS9VJgyAdivR6J1Hz14jSuBJOj8Bpdu+g4fV45LRSeS8A@mail.gmail.com","subject":"Re: I still heavily use git whatchanged after more than 10 years","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2026-04-16T17:18:00Z","receivedAt":"2026-04-16T17:18:04Z","isPatch":false,"body":"Chester <just13.0818@gmail.com> writes:\n\n> Dear Git developers,\n>\n> I saw the message that git whatchanged is now nominated for removal\n> and requires the --i-still-use-this flag.\n\nYou should have seen:\n\n    $ git whatchanged\n    'git whatchanged' is nominated for removal.\n\n    hint: You can replace 'git whatchanged <opts>' with:\n    hint:\tgit log <opts> --raw --no-merges\n    hint: Or make an alias:\n    hint:\tgit config set --global alias.whatchanged 'log --raw --no-merges'\n\n    If you still use this command, here's what you can do:\n\n    - read https://git-scm.com/docs/BreakingChanges.html\n    - check if anyone has discussed this on the mailing\n      list and if they came up with something that can\n      help you: https://lore.kernel.org/git/?q=git%20whatchanged\n    - send an email to <git@vger.kernel.org> to let us\n      know that you still use this command and were unable\n      to determine a suitable replacement\n\n    fatal: refusing to run without --i-still-use-this\n\n> I understand that it can be replaced with git log --raw --no-merges,\n> but after so many years, git whatchanged just feels more natural and\n> quicker to type for my use case.\n\nYou are asked to send a message to this list whene you were unable\nto determine a suitable replacement, but it is hard to believe that\nis the case with your use case.\n\nThe \"alias\" hint above seems to give exactly the suitable\nreplacement to help folks who cannot adjust due to the muscle\nmemory.\n\n"}]}