From: Junio C Hamano <gitster@pobox.com>
To: "Kristoffer Haugsbakk" <kristofferhaugsbakk@fastmail.com>
Cc: git@vger.kernel.org
Subject: Re: I still use git whatchanged
Date: Mon, 29 Sep 2025 07:16:36 -0700 [thread overview]
Message-ID: <xmqq8qhx5oor.fsf@gitster.g> (raw)
In-Reply-To: <971c5431-f203-41b6-a629-e06480afbf1e@app.fastmail.com> (Kristoffer Haugsbakk's message of "Mon, 29 Sep 2025 10:58:17 +0200")
"Kristoffer Haugsbakk" <kristofferhaugsbakk@fastmail.com> writes:
> On Mon, Sep 29, 2025, at 10:42, Henrik Bennin wrote:
>> May I ask not to remove git whatchanged because I still use it regularly?
>
> What the error message you got doesn’t say is that you can use
> git-log(1) instead. It supports everything that git-whatchanged(1)
> supports.
>
> • 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.
We probably should merge kh/you-still-use-whatchanged-fix to produce
Git 2.51.1 sooner.
Thanks.
next prev parent reply other threads:[~2025-09-29 14:16 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-29 8:42 I still use git whatchanged Henrik Bennin
2025-09-29 8:58 ` Kristoffer Haugsbakk
2025-09-29 14:16 ` Junio C Hamano [this message]
[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-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=xmqq8qhx5oor.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=kristofferhaugsbakk@fastmail.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;
as well as URLs for NNTP newsgroup(s).