{"thread":{"id":"64522","subject":"git whatchanged deprecation","startedAt":"2025-11-23T22:00:59Z","lastAt":"2025-11-24T08:38:09Z","messageCount":2,"participants":["Daniel Hammer","Kristoffer Haugsbakk"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"531202","messageId":"CALrqSpeAiSU5JtdePf1Haygd_a08AKu6iBrO-LZDjcW8KCqJLg@mail.gmail.com","threadId":"64522","inReplyTo":null,"subject":"git whatchanged deprecation","fromName":"Daniel Hammer","fromEmail":"daniel.hammer@gmail.com","sentAt":"2025-11-23T22:00:32Z","receivedAt":"2025-11-23T22:00:59Z","isPatch":false,"sender":{"key":"daniel.hammer@gmail.com","avatar":null},"body":"Hi git devs,\n\nRegarding:\n> $ git whatchanged\n> 'git whatchanged' is nominated for removal.\n> If you still use this command, please add an extra\n> option, '--i-still-use-this', on the command line\n> and let us know you still use it by sending an e-mail\n> to <git@vger.kernel.org>.  Thanks.\n> fatal: refusing to run without --i-still-use-this\n\nI still use this, usually multiple times a day.\n\n\nThe flag approach seems unnecessarily heavy handed, when amending the\ndocumentation would have sufficed.\n\nAs far as I can tell from the documentation, this is just shorthand\nfor a(nother) counter-intuitive git command.\n\nHope this DevEx regression is reversed ASAP.\n\nThanks in advance,\n\nDH\n"},{"id":"531206","messageId":"26c59938-45b5-4dcf-924c-49a3d354126b@app.fastmail.com","threadId":"64522","inReplyTo":"CALrqSpeAiSU5JtdePf1Haygd_a08AKu6iBrO-LZDjcW8KCqJLg@mail.gmail.com","subject":"Re: git whatchanged deprecation","fromName":"Kristoffer Haugsbakk","fromEmail":"kristofferhaugsbakk@fastmail.com","sentAt":"2025-11-24T08:36:23Z","receivedAt":"2025-11-24T08:38:09Z","isPatch":false,"sender":{"key":"kristofferhaugsbakk@fastmail.com","avatar":null},"body":"On Sun, Nov 23, 2025, at 23:00, Daniel Hammer wrote:\n> Regarding:\n>> $ git whatchanged\n>> 'git whatchanged' is nominated for removal.\n>> If you still use this command, please add an extra\n>> option, '--i-still-use-this', on the command line\n>> and let us know you still use it by sending an e-mail\n>> to <git@vger.kernel.org>.  Thanks.\n>> fatal: refusing to run without --i-still-use-this\n>\n> I still use this, usually multiple times a day.\n>\n>\n> The flag approach seems unnecessarily heavy handed, when amending the\n> documentation would have sufficed.\n\nThis was added to the documentation in 2013:\n\n    New users are encouraged to use [git-log(1)] instead. ...\n\n    The command is primarily kept for historical reasons; ...\n\nThe version you are on (2.51.0) finally said that it was deprecated.\n\nThe heavy-handed `--i-still-use-this` is meant to alert users (who may\nnot read the updated documentation) that the command is going away.\n\nBreaking changes overall are documented in\nhttps://git-scm.com/docs/BreakingChanges\n\n> As far as I can tell from the documentation, this is just shorthand\n> for a(nother) counter-intuitive git command.\n\nThen you know that `git whatchanged` can be replaced with `git log\n--raw`. Well, a closer equivalent is\n\n    git log --raw --no-merges\n\nBut you can keep typing `git whatchanged` on Git versions 2.51.1,\n2.51.2, and 2.52.0 by setting up an alias with that name:\n\n    git config set --global alias.whatchanged 'log --raw --no-merges'\n\n> Hope this DevEx regression is reversed ASAP.\n\nThat won’t happen.\n"}]}