Hey,
I still use git whatchanged
Thanks, Chris
Re: git whatchanged
Also, my initial email was blocked for being HTML. In future deprecation messages, I think it'd be helpful to include https://subspace.kernel.org/etiquette.html up front if the emails will be subject to those rules. Seeing a blocked email when I'm just trying to follow the instructions you gave me is an unpleasant experience, and I'd imagine it dissuades some folks from giving you feedback.
Thanks for considering that, Chris
On Tue, Aug 19, 2025 at 12:51 PM Chris Judkins-Fisher <chris.judkins-fisher@donorschoose.org> wrote:
Show 7 quoted lines
> > Hey, > > I still use git whatchanged > > Thanks, > Chris
rsbecker@nexbridge.comRE: git whatchanged
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.
Re: git whatchanged
On Tue, Aug 19, 2025, at 22:57, rsbecker@nexbridge.com wrote:
Show 15 quoted lines
> 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.
-- Kristoffer Haugsbakk
rsbecker@nexbridge.comRE: git whatchanged
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.
Junio C HamanoRe: git whatchanged
"Kristoffer Haugsbakk" <kristofferhaugsbakk@fastmail.com> writes:
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.
Not quite.
$ git -c alias.whatchanged='!echo bar' \ whatchanged --i-still-use-this -2 --oneline 7c10e48e81 describe: pass commit to describe_commit() :100644 100644 72b2e1162c 04df89d56b M builtin/describe.c 8cfd4ac215 describe: handle blob traversal with no commits :100644 100644 f7bea3c8c5 72b2e1162c M builtin/describe.c :100755 100755 feec57bcbc 2c70cc561a M t/t6120-describe.sh
Your alias with the same name as a real command is silently ignored, and when the real command disappears, it will start working.
Having said that, as "log --raw" is even shorter to type than "whatchanged", these people are really better off without such an alias.
Re: git whatchanged
What I actually type is "git wh<tab>". That does result in less typing for me than "git log --raw" would. For now I've added the following alias, which takes precedence over the full "whatchanged" completion: whatchange = "log --raw"
On Wed, Aug 20, 2025 at 11:49 AM Junio C Hamano <gitster@pobox.com> wrote:
Show 39 quoted lines
> > "Kristoffer Haugsbakk" <kristofferhaugsbakk@fastmail.com> writes: > > > 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. > > Not quite. > > $ git -c alias.whatchanged='!echo bar' \ > whatchanged --i-still-use-this -2 --oneline > 7c10e48e81 describe: pass commit to describe_commit() > :100644 100644 72b2e1162c 04df89d56b M builtin/describe.c > 8cfd4ac215 describe: handle blob traversal with no commits > :100644 100644 f7bea3c8c5 72b2e1162c M builtin/describe.c > :100755 100755 feec57bcbc 2c70cc561a M t/t6120-describe.sh > > Your alias with the same name as a real command is silently ignored, > and when the real command disappears, it will start working. > > Having said that, as "log --raw" is even shorter to type than > "whatchanged", these people are really better off without such an > alias.
Re: git whatchanged
On Wed, Aug 20, 2025, at 18:49, Junio C Hamano wrote:
> Your alias with the same name as a real command is silently ignored, > and when the real command disappears, it will start working.
That’s what I intended to mean.
> Having said that, as "log --raw" is even shorter to type than > "whatchanged", these people are really better off without such an > alias.
I’m wondering based on the emails so far if the error message should spell out that (1) you can help yourself beyond reporting i-still-use-this and specifically that (2) there is a git-log(1) equivalent (like git-whatchanged(1) says).
The message itself reads like it could be read like: tell us and we might put the brakes on removing it (and that’s it).
-- still my
Junio C HamanoRe: git whatchanged
"Kristoffer Haugsbakk" <kristofferhaugsbakk@fastmail.com> writes:
> The message itself reads like it could be read like: tell us and we > might put the brakes on removing it (and that’s it).
Yeah, that is a wrong interpretation we did not want to trigger.
"If you are a developer of a script that uses whatchanged, then rewrite it with 'log --raw --no-merges' and be happy. If the script is very widely used, dropping us a note would be nice, as we can redirect end-user inquiries of your script towards you. If you are an end-user of such a script, bug your supplier of such a script. Thanks."
perhaps?
Re: git whatchanged
On Wed, Aug 20, 2025, at 23:10, Junio C Hamano wrote:
Show 15 quoted lines
> "Kristoffer Haugsbakk" <kristofferhaugsbakk@fastmail.com> writes: > >> The message itself reads like it could be read like: tell us and we >> might put the brakes on removing it (and that’s it). > > Yeah, that is a wrong interpretation we did not want to trigger. > > "If you are a developer of a script that uses whatchanged, then > rewrite it with 'log --raw --no-merges' and be happy. If the script > is very widely used, dropping us a note would be nice, as we can > redirect end-user inquiries of your script towards you. If you are > an end-user of such a script, bug your supplier of such a script. > Thanks." > > perhaps?
That looks like it covers all the bases. Great.
-- Kristoffer Haugsbakk