From: Junio C Hamano <gitster@pobox•com>
To: "Chirayu Desai" <git@cdesai•in>
Cc: git@vger•kernel.org
Subject: Re: Using command nominated for removal: whatchanged
Date: Wed, 10 Sep 2025 13:08:51 -0700 [thread overview]
Message-ID: <xmqq8qimrrxo.fsf@gitster.g> (raw)
In-Reply-To: <b32a369f-87c9-41f6-b1cb-81273945dc17@app.fastmail.com> (Chirayu Desai's message of "Wed, 10 Sep 2025 19:08:24 +0530")
"Chirayu Desai" <git@cdesai•in> writes:
> Hello,
>
> Hope this email finds you well!
>
> 'git whatchanged' is nominated for removal.
>
> I still use this command. I usually run 'git whatchanged -1' and 'git whatchanged <commit>' to quickly see what files have changed in a particular commit.
>
> I guess there might be some alias I could setup to achieve the same - it's more that this command has become a muscle memory at this point so I kept hitting the removal message, and here I am.
Thanks for letting us know. If you still use it, you can retrain
your fingers to use "git log" with some options instead. The most
literal translation would be "git log --raw --no-merges", but there
are MUCH BETTER options invented since "whatchanged" was written.
If the reason you are interested in is to learn the names of the
files, then "git log --names-only" gives a lot cleaner output
without hexadecimal gibberish that has not much use for human
readers, for examplle.
prev parent reply other threads:[~2025-09-10 20:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-10 13:38 Using command nominated for removal: whatchanged Chirayu Desai
2025-09-10 13:53 ` Kristoffer Haugsbakk
2025-09-10 20:08 ` 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=xmqq8qimrrxo.fsf@gitster.g \
--to=gitster@pobox$(echo .)com \
--cc=git@cdesai$(echo .)in \
--cc=git@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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