From: <rsbecker@nexbridge.com>
To: "'Kristoffer Haugsbakk'" <kristofferhaugsbakk@fastmail.com>,
"'Chris Judkins-Fisher'" <chris.judkins-fisher@donorschoose.org>,
<git@vger.kernel.org>
Subject: RE: git whatchanged
Date: Wed, 20 Aug 2025 10:12:57 -0400 [thread overview]
Message-ID: <015e01dc11dc$8aad1af0$a00750d0$@nexbridge.com> (raw)
In-Reply-To: <37da14fb-fead-448b-b6a0-853c9fbea653@app.fastmail.com>
On August 20, 2025 3:53 AM, Kristoffer Haugsbakk wrote:
>On Tue, Aug 19, 2025, at 22:57, rsbecker@nexbridge.com wrote:
>> On August 19, 2025 1:51 PM, Chris Judkins-Fisher wrote:
>>>I still use git whatchanged
>>
>> I did too. However, now that git log --since has basically the same
>> functionality, Perhaps setting up a git alias might do the trick for
>> you:
>>
>> git config --global alias.whatchanged 'log'
>>
>> so
>>
>> git whatchanged --since="2 week"
>>
>> or something like that should continue to work after the command is
>> removed.
>
>You can’t alias core commands. So this will fail in the reported way before Git 3.0.
>Then from that point out it will work as an alias.
I know. I was being pro-active with my answer on how to deal with this.
next prev parent reply other threads:[~2025-08-20 14:13 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-19 17:51 git whatchanged Chris Judkins-Fisher
2025-08-19 17:59 ` Chris Judkins-Fisher
2025-08-19 20:57 ` rsbecker
2025-08-20 7:52 ` Kristoffer Haugsbakk
2025-08-20 14:12 ` rsbecker [this message]
2025-08-20 16:49 ` Junio C Hamano
2025-08-20 17:05 ` Chris Judkins-Fisher
2025-08-20 20:58 ` Kristoffer Haugsbakk
2025-08-20 21:10 ` Junio C Hamano
2025-08-20 21:11 ` Kristoffer Haugsbakk
-- strict thread matches above, loose matches on Subject: below --
2025-08-26 13:04 Chris Palmer
2025-08-26 13:54 ` Kristoffer Haugsbakk
2025-09-03 15:34 Jesse Hathaway
2025-09-03 19:56 ` Junio C Hamano
2025-09-03 20:43 ` Kristoffer Haugsbakk
2025-09-03 21:47 ` Junio C Hamano
2025-09-04 23:45 Michael Tourigny (TERAWE CORPORATION)
2025-09-10 20:49 Jose Jaramillo
2025-09-10 21:03 ` Kristoffer Haugsbakk
2025-09-10 21:15 ` Jose Jaramillo
2025-09-26 1:00 Neal Miller
2025-09-26 7:13 ` Kristoffer Haugsbakk
2025-09-26 15:54 ` Junio C Hamano
2025-09-28 1:12 ` Neal Miller
2025-10-02 6:48 Jiří Bašek
2025-10-02 7:12 ` Kristoffer Haugsbakk
2025-10-08 14:20 Git whatchanged Filippo Falezza
2025-10-08 14:42 ` Kristoffer Haugsbakk
2025-10-13 12:44 git whatchanged Grzegorz Koperwas
2025-10-13 13:47 ` Kristoffer Haugsbakk
2025-10-16 12:16 Julian Squires
2025-10-16 13:27 ` Kristoffer Haugsbakk
2025-10-31 8:02 Remke Schuurmans
2025-10-31 8:23 ` Kristoffer Haugsbakk
[not found] ` <c2551c49-bcb4-4518-97d3-063941d591e8@gmail.com>
2025-10-31 9:13 ` Kristoffer Haugsbakk
2025-11-07 11:40 Franz Brauße
2025-11-07 13:11 ` Kristoffer Haugsbakk
2025-11-07 14:16 ` Franz Brauße
2025-11-07 14:30 ` 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='015e01dc11dc$8aad1af0$a00750d0$@nexbridge.com' \
--to=rsbecker@nexbridge.com \
--cc=chris.judkins-fisher@donorschoose.org \
--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 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.