From: Junio C Hamano <gitster@pobox.com>
To: "Harding, Mitch Perry (The weird one)" <mitchell.harding@hpe.com>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: I still use "git whatchanged"
Date: Mon, 25 Aug 2025 16:40:17 -0700 [thread overview]
Message-ID: <xmqqwm6rm0m6.fsf@gitster.g> (raw)
In-Reply-To: <IA1PR84MB3012CE550D803A3C3CC5572D873EA@IA1PR84MB3012.NAMPRD84.PROD.OUTLOOK.COM> (Mitch Perry Harding's message of "Mon, 25 Aug 2025 19:12:11 +0000")
"Harding, Mitch Perry (The weird one)" <mitchell.harding@hpe.com>
writes:
> Sending this email as requested by my friendly git binary.
Thanks. As your friendly git binary should have (but did not)
suggested, please switch to a more modern variants like "git log
--raw" (or --stat that may give even more useful information).
next prev parent reply other threads:[~2025-08-25 23:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-25 19:12 I still use "git whatchanged" Harding, Mitch Perry (The weird one)
2025-08-25 23:40 ` Junio C Hamano [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-10-22 16:05 I still use `git whatchanged` Benjamin Root
2025-10-23 18:05 ` 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=xmqqwm6rm0m6.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=mitchell.harding@hpe.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).