From: Kristoffer Haugsbakk Date: Thu, 27 Aug 2026 06:08:11 GMT Subject: Re: Whatchanged —i-still-use-this Message-ID: <9dca592c-c683-4cf4-b7c4-e08c338e7582@app.fastmail.com> In-Reply-To: <779B6ED0-EA2F-4CCE-9616-BFA958DEC560@gmail.com> On Wed, Aug 26, 2026, at 14:12, edvard.jo@gmail.com wrote: > Hi! > > Answers inline: > >> 26 aug. 2026 kl. 09:47 skrev Kristoffer Haugsbakk : >> >> Hi >> >>> On Wed, Aug 26, 2026, at 09:18, edvard.jo@gmail.com wrote: >>> I was encouraged by git cli to send you an email when using the command >>> ”whatchanged” that now needs ”—i-still-use-this”. >> >> Are you running Git v2.51.0 or something? > Correct! I wasn’t aware since it was on a server I don’t maintain. I > checked version now and it was 2.51.0. > >> That older message (since >> updated) does ask you to send an email with no ifs and buts: >> >> '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 . Thanks. >> >> But the updated one has some alternatives: >> >> 'git whatchanged' is nominated for removal. >> >> hint: You can replace 'git whatchanged ' with: >> hint: git log --raw --no-merges >> hint: Or make an alias: >> hint: git config set --global alias.whatchanged 'log --raw --no-merges' >> >> If you still use this command, here's what you can do: >> >> - read https://git-scm.com/docs/BreakingChanges.html >> - check if anyone has discussed this on the mailing >> list and if they came up with something that can >> help you: https://lore.kernel.org/git/?q=git%20whatchanged >> - send an email to to let us >> know that you still use this command and were unable >> to determine a suitable replacement >> >> fatal: refusing to run without --i-still-use-this >> >>> >>> For my purposes, I could instead use >>> git log —oneline —name-status >>> Or >>> git diff —stat main >> >> Yeah, those are similar, and more “human friendly” than `--raw`. What do >> you like about the command, the specific output or the command name >> itself (muscle memory maybe)? If it’s the latter, you can make an alias >> with more human friendly options than `--raw`: >> >> git config set --global alias.whatchanged 'log --stat --no-merges' > Yes I mainly use it because it’s easier to remember and can be > tab-completed very quickly. As long as I see file names I’m happy. So > yes, alias will work great for me! Good. Just remember to Reply All so that it goes to the Git list as well. Thanks