RE: git whatchanged

From: rsbecker@nexbridge.com <rsbecker@nexbridge.com>
Date: Aug 20, 2025, 14:12 UTC
Message-ID: <015e01dc11dc$8aad1af0$a00750d0$@nexbridge.com>
In-Reply-To: <37da14fb-fead-448b-b6a0-853c9fbea653@app.fastmail.com>

On August 20, 2025 3:53 AM, Kristoffer Haugsbakk wrote:

Show 19 quoted lines

>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.