From: Junio C Hamano <gitster@pobox.com>
To: Chester <just13.0818@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: I still heavily use git whatchanged after more than 10 years
Date: Thu, 16 Apr 2026 10:18:00 -0700 [thread overview]
Message-ID: <xmqqtsta259z.fsf@gitster.g> (raw)
In-Reply-To: <CAHvvhRS9VJgyAdivR6J1Hz14jSuBJOj8Bpdu+g4fV45LRSeS8A@mail.gmail.com> (Chester's message of "Fri, 17 Apr 2026 01:06:40 +0800")
Chester <just13.0818@gmail.com> writes:
> Dear Git developers,
>
> I saw the message that git whatchanged is now nominated for removal
> and requires the --i-still-use-this flag.
You should have seen:
$ git whatchanged
'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
> I understand that it can be replaced with git log --raw --no-merges,
> but after so many years, git whatchanged just feels more natural and
> quicker to type for my use case.
You are asked to send a message to this list whene you were unable
to determine a suitable replacement, but it is hard to believe that
is the case with your use case.
The "alias" hint above seems to give exactly the suitable
replacement to help folks who cannot adjust due to the muscle
memory.
prev parent reply other threads:[~2026-04-16 17:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-16 17:06 I still heavily use git whatchanged after more than 10 years Chester
2026-04-16 17:18 ` Junio C Hamano [this message]
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=xmqqtsta259z.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=just13.0818@gmail.com \
/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