Git development
 help / color / mirror / Atom feed
From: "Kristoffer Haugsbakk" <kristofferhaugsbakk@fastmail.com>
To: edvard.jo@gmail.com, git@vger.kernel.org
Subject: Re: Whatchanged —i-still-use-this
Date: Wed, 26 Aug 2026 09:46:38 +0200	[thread overview]
Message-ID: <03ce12c7-a0c1-43a9-9198-ace60c8ba9a8@app.fastmail.com> (raw)
In-Reply-To: <3505ADD2-C8D9-497C-B8F3-F7FB46696525@gmail.com>

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? 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 <git@vger.kernel.org>.  Thanks.

But the updated one has some alternatives:

    'git whatchanged' is nominated for removal.

    hint: You can replace 'git whatchanged <opts>' with:
    hint:   git log <opts> --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 <git@vger.kernel.org> 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'

  reply	other threads:[~2026-08-26  7:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-26  7:18 Whatchanged —i-still-use-this edvard.jo
2026-08-26  7:46 ` Kristoffer Haugsbakk [this message]
     [not found]   ` <779B6ED0-EA2F-4CCE-9616-BFA958DEC560@gmail.com>
2026-08-27  6:08     ` Kristoffer Haugsbakk

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=03ce12c7-a0c1-43a9-9198-ace60c8ba9a8@app.fastmail.com \
    --to=kristofferhaugsbakk@fastmail.com \
    --cc=edvard.jo@gmail.com \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox