From: "Kristoffer Haugsbakk" <kristofferhaugsbakk@fastmail.com>
To: "Wayne Rowcliffe" <wrowclif@gmail.com>, git@vger.kernel.org
Subject: Re: I still use git whatchanged
Date: Mon, 05 Jan 2026 20:23:26 +0100 [thread overview]
Message-ID: <1ee133df-2bb0-4aaa-b628-e7e2655d4332@app.fastmail.com> (raw)
In-Reply-To: <CANG6c1XhaL1poT2Myo2sy4xbu86vAXO0xQKe33vg7pERmx=TbA@mail.gmail.com>
On Mon, Jan 5, 2026, at 19:05, Wayne Rowcliffe wrote:
> I tried using git whatchanged, which I use probably daily, and it said
> I needed to send you an email that I use it.
>
> It's very handy for figuring out what files changed in a commit.
This command is being removed because it was supplanted by git-log(1) a
long while ago. Both commands use the same machinery, just with
different defaults.
You can replace it with `git log` in this way:
• Given: `git whatchanged <opts>`
• Replace with: `git log <opts> --no-merges --raw`
Additionally for the sake of readability, you might have more
use for `--stat` or `--name-only` rather than `--raw` if you are only
reading the output (not feding the output to another program).
next prev parent reply other threads:[~2026-01-05 19:23 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-05 18:05 I still use git whatchanged Wayne Rowcliffe
2026-01-05 19:23 ` Kristoffer Haugsbakk [this message]
2026-01-05 19:26 ` Wayne Rowcliffe
[not found] <CAOFvV7kFm-A2_i2URg-2wgfTet8Dv9SMAD0Aw1AwStCJm5WOLA@mail.gmail.com>
2025-12-07 10:12 ` Lee Smith
2025-12-07 11:56 ` Kristoffer Haugsbakk
-- strict thread matches above, loose matches on Subject: below --
2025-11-15 3:16 Chia-Sheng Chang
2025-11-15 14:55 ` Kristoffer Haugsbakk
2025-10-13 21:59 Samer Abdallah
2025-10-13 22:15 ` Kristoffer Haugsbakk
2025-10-14 1:06 ` Junio C Hamano
[not found] ` <25428D84-1B92-4398-93B2-175231A699B4@gmail.com>
2025-10-14 7:10 ` Kristoffer Haugsbakk
2025-09-29 8:42 Henrik Bennin
2025-09-29 8:58 ` Kristoffer Haugsbakk
2025-09-29 14:16 ` Junio C Hamano
2025-08-26 12:42 Mira Skwar
2025-08-26 13:56 ` 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=1ee133df-2bb0-4aaa-b628-e7e2655d4332@app.fastmail.com \
--to=kristofferhaugsbakk@fastmail.com \
--cc=git@vger.kernel.org \
--cc=wrowclif@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.