{"thread":{"id":"63990","subject":"git whatchanged","startedAt":"2025-08-19T17:51:20Z","lastAt":"2025-08-20T21:12:16Z","messageCount":10,"participants":["Chris Judkins-Fisher","rsbecker@nexbridge.com","Kristoffer Haugsbakk","Junio C Hamano"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"524459","messageId":"CAAn3O_2n75RGpvxv1o14BE3KFdwiJW9OOKaHp6_c0rd_MqxC2Q@mail.gmail.com","threadId":"63990","inReplyTo":null,"subject":"git whatchanged","fromName":"Chris Judkins-Fisher","fromEmail":"chris.judkins-fisher@donorschoose.org","sentAt":"2025-08-19T17:51:07Z","receivedAt":"2025-08-19T17:51:20Z","isPatch":false,"sender":{"key":"chris.judkins-fisher@donorschoose.org","avatar":null},"body":"Hey,\n\nI still use git whatchanged\n\nThanks,\nChris\n"},{"id":"524460","messageId":"CAAn3O_1+4EUcD+5WBY6-TwPCboVTikBZzGYN-QTJYVEiSaitPQ@mail.gmail.com","threadId":"63990","inReplyTo":"CAAn3O_2n75RGpvxv1o14BE3KFdwiJW9OOKaHp6_c0rd_MqxC2Q@mail.gmail.com","subject":"Re: git whatchanged","fromName":"Chris Judkins-Fisher","fromEmail":"chris.judkins-fisher@donorschoose.org","sentAt":"2025-08-19T17:59:27Z","receivedAt":"2025-08-19T17:59:41Z","isPatch":false,"sender":{"key":"chris.judkins-fisher@donorschoose.org","avatar":null},"body":"Also, my initial email was blocked for being HTML. In future\ndeprecation messages, I think it'd be helpful to include\nhttps://subspace.kernel.org/etiquette.html up front if the emails will\nbe subject to those rules. Seeing a blocked email when I'm just trying\nto follow the instructions you gave me is an unpleasant experience,\nand I'd imagine it dissuades some folks from giving you feedback.\n\nThanks for considering that,\nChris\n\n\nOn Tue, Aug 19, 2025 at 12:51 PM Chris Judkins-Fisher\n<chris.judkins-fisher@donorschoose.org> wrote:\n>\n> Hey,\n>\n> I still use git whatchanged\n>\n> Thanks,\n> Chris\n"},{"id":"524486","messageId":"011801dc114b$f38bb130$daa31390$@nexbridge.com","threadId":"63990","inReplyTo":"CAAn3O_2n75RGpvxv1o14BE3KFdwiJW9OOKaHp6_c0rd_MqxC2Q@mail.gmail.com","subject":"RE: git whatchanged","fromName":"","fromEmail":"rsbecker@nexbridge.com","sentAt":"2025-08-19T20:57:56Z","receivedAt":"2025-08-19T20:58:08Z","isPatch":false,"sender":{"key":"randall.becker@nexbridge.ca","avatar":"https://avatars.githubusercontent.com/u/28956764?v=4"},"body":"On August 19, 2025 1:51 PM, Chris Judkins-Fisher wrote:\n>I still use git whatchanged\n\nI did too. However, now that git log --since has basically the same functionality,\nPerhaps setting up a git alias might do the trick for you:\n\ngit config --global alias.whatchanged 'log'\n\nso\n\ngit whatchanged --since=\"2 week\"\n\nor something like that should continue to work after the command is\nremoved.\n\n"},{"id":"524514","messageId":"37da14fb-fead-448b-b6a0-853c9fbea653@app.fastmail.com","threadId":"63990","inReplyTo":"011801dc114b$f38bb130$daa31390$@nexbridge.com","subject":"Re: git whatchanged","fromName":"Kristoffer Haugsbakk","fromEmail":"kristofferhaugsbakk@fastmail.com","sentAt":"2025-08-20T07:52:35Z","receivedAt":"2025-08-20T07:53:03Z","isPatch":false,"sender":{"key":"kristofferhaugsbakk@fastmail.com","avatar":null},"body":"On Tue, Aug 19, 2025, at 22:57, rsbecker@nexbridge.com wrote:\n> On August 19, 2025 1:51 PM, Chris Judkins-Fisher wrote:\n>>I still use git whatchanged\n>\n> I did too. However, now that git log --since has basically the same\n> functionality,\n> Perhaps setting up a git alias might do the trick for you:\n>\n> git config --global alias.whatchanged 'log'\n>\n> so\n>\n> git whatchanged --since=\"2 week\"\n>\n> or something like that should continue to work after the command is\n> removed.\n\nYou can’t alias core commands.  So this will fail in the reported way\nbefore Git 3.0.  Then from that point out it will work as an alias.\n\n-- \nKristoffer Haugsbakk\n"},{"id":"524527","messageId":"015e01dc11dc$8aad1af0$a00750d0$@nexbridge.com","threadId":"63990","inReplyTo":"37da14fb-fead-448b-b6a0-853c9fbea653@app.fastmail.com","subject":"RE: git whatchanged","fromName":"","fromEmail":"rsbecker@nexbridge.com","sentAt":"2025-08-20T14:12:57Z","receivedAt":"2025-08-20T14:13:07Z","isPatch":false,"sender":{"key":"randall.becker@nexbridge.ca","avatar":"https://avatars.githubusercontent.com/u/28956764?v=4"},"body":"On August 20, 2025 3:53 AM, Kristoffer Haugsbakk wrote:\n>On Tue, Aug 19, 2025, at 22:57, rsbecker@nexbridge.com wrote:\n>> On August 19, 2025 1:51 PM, Chris Judkins-Fisher wrote:\n>>>I still use git whatchanged\n>>\n>> I did too. However, now that git log --since has basically the same\n>> functionality, Perhaps setting up a git alias might do the trick for\n>> you:\n>>\n>> git config --global alias.whatchanged 'log'\n>>\n>> so\n>>\n>> git whatchanged --since=\"2 week\"\n>>\n>> or something like that should continue to work after the command is\n>> removed.\n>\n>You can’t alias core commands.  So this will fail in the reported way before Git 3.0.\n>Then from that point out it will work as an alias.\n\nI know. I was being pro-active with my answer on how to deal with this.\n\n"},{"id":"524535","messageId":"xmqqfrdmaqg4.fsf@gitster.g","threadId":"63990","inReplyTo":"37da14fb-fead-448b-b6a0-853c9fbea653@app.fastmail.com","subject":"Re: git whatchanged","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2025-08-20T16:49:31Z","receivedAt":"2025-08-20T16:49:35Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"\"Kristoffer Haugsbakk\" <kristofferhaugsbakk@fastmail.com> writes:\n\n> On Tue, Aug 19, 2025, at 22:57, rsbecker@nexbridge.com wrote:\n>> On August 19, 2025 1:51 PM, Chris Judkins-Fisher wrote:\n>>>I still use git whatchanged\n>>\n>> I did too. However, now that git log --since has basically the same\n>> functionality,\n>> Perhaps setting up a git alias might do the trick for you:\n>>\n>> git config --global alias.whatchanged 'log'\n>>\n>> so\n>>\n>> git whatchanged --since=\"2 week\"\n>>\n>> or something like that should continue to work after the command is\n>> removed.\n>\n> You can’t alias core commands.  So this will fail in the reported way\n> before Git 3.0.  Then from that point out it will work as an alias.\n\nNot quite.\n\n  $ git -c alias.whatchanged='!echo bar' \\\n\twhatchanged --i-still-use-this -2 --oneline\n  7c10e48e81 describe: pass commit to describe_commit()\n  :100644 100644 72b2e1162c 04df89d56b M\tbuiltin/describe.c\n  8cfd4ac215 describe: handle blob traversal with no commits\n  :100644 100644 f7bea3c8c5 72b2e1162c M\tbuiltin/describe.c\n  :100755 100755 feec57bcbc 2c70cc561a M\tt/t6120-describe.sh\n\nYour alias with the same name as a real command is silently ignored,\nand when the real command disappears, it will start working.\n\nHaving said that, as \"log --raw\" is even shorter to type than\n\"whatchanged\", these people are really better off without such an\nalias.\n"},{"id":"524539","messageId":"CAAn3O_2iHVt5TctvwLLSXm5Nw2wS8e9Xk0is1=k=-qRS=gHVMQ@mail.gmail.com","threadId":"63990","inReplyTo":"xmqqfrdmaqg4.fsf@gitster.g","subject":"Re: git whatchanged","fromName":"Chris Judkins-Fisher","fromEmail":"chris.judkins-fisher@donorschoose.org","sentAt":"2025-08-20T17:05:54Z","receivedAt":"2025-08-20T17:06:09Z","isPatch":false,"sender":{"key":"chris.judkins-fisher@donorschoose.org","avatar":null},"body":"What I actually type is \"git wh<tab>\". That does result in less typing\nfor me than \"git log --raw\" would. For now I've added the following\nalias, which takes precedence over the full \"whatchanged\" completion:\nwhatchange = \"log --raw\"\n\n\nOn Wed, Aug 20, 2025 at 11:49 AM Junio C Hamano <gitster@pobox.com> wrote:\n>\n> \"Kristoffer Haugsbakk\" <kristofferhaugsbakk@fastmail.com> writes:\n>\n> > On Tue, Aug 19, 2025, at 22:57, rsbecker@nexbridge.com wrote:\n> >> On August 19, 2025 1:51 PM, Chris Judkins-Fisher wrote:\n> >>>I still use git whatchanged\n> >>\n> >> I did too. However, now that git log --since has basically the same\n> >> functionality,\n> >> Perhaps setting up a git alias might do the trick for you:\n> >>\n> >> git config --global alias.whatchanged 'log'\n> >>\n> >> so\n> >>\n> >> git whatchanged --since=\"2 week\"\n> >>\n> >> or something like that should continue to work after the command is\n> >> removed.\n> >\n> > You can’t alias core commands.  So this will fail in the reported way\n> > before Git 3.0.  Then from that point out it will work as an alias.\n>\n> Not quite.\n>\n>   $ git -c alias.whatchanged='!echo bar' \\\n>         whatchanged --i-still-use-this -2 --oneline\n>   7c10e48e81 describe: pass commit to describe_commit()\n>   :100644 100644 72b2e1162c 04df89d56b M        builtin/describe.c\n>   8cfd4ac215 describe: handle blob traversal with no commits\n>   :100644 100644 f7bea3c8c5 72b2e1162c M        builtin/describe.c\n>   :100755 100755 feec57bcbc 2c70cc561a M        t/t6120-describe.sh\n>\n> Your alias with the same name as a real command is silently ignored,\n> and when the real command disappears, it will start working.\n>\n> Having said that, as \"log --raw\" is even shorter to type than\n> \"whatchanged\", these people are really better off without such an\n> alias.\n"},{"id":"524563","messageId":"790a24b0-a799-44dd-b97d-c4c24e5d23a8@app.fastmail.com","threadId":"63990","inReplyTo":"xmqqfrdmaqg4.fsf@gitster.g","subject":"Re: git whatchanged","fromName":"Kristoffer Haugsbakk","fromEmail":"kristofferhaugsbakk@fastmail.com","sentAt":"2025-08-20T20:58:18Z","receivedAt":"2025-08-20T20:58:43Z","isPatch":false,"sender":{"key":"kristofferhaugsbakk@fastmail.com","avatar":null},"body":"On Wed, Aug 20, 2025, at 18:49, Junio C Hamano wrote:\n> Your alias with the same name as a real command is silently ignored,\n> and when the real command disappears, it will start working.\n\nThat’s what I intended to mean.\n\n> Having said that, as \"log --raw\" is even shorter to type than\n> \"whatchanged\", these people are really better off without such an\n> alias.\n\nI’m wondering based on the emails so far if the error message should\nspell out that (1) you can help yourself beyond reporting\ni-still-use-this and specifically that (2) there is a git-log(1)\nequivalent (like git-whatchanged(1) says).\n\nThe message itself reads like it could be read like: tell us and we\nmight put the brakes on removing it (and that’s it).\n\n-- \nstill my\n"},{"id":"524568","messageId":"xmqqsehl8zt8.fsf@gitster.g","threadId":"63990","inReplyTo":"790a24b0-a799-44dd-b97d-c4c24e5d23a8@app.fastmail.com","subject":"Re: git whatchanged","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2025-08-20T21:10:11Z","receivedAt":"2025-08-20T21:10:14Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"\"Kristoffer Haugsbakk\" <kristofferhaugsbakk@fastmail.com> writes:\n\n> The message itself reads like it could be read like: tell us and we\n> might put the brakes on removing it (and that’s it).\n\nYeah, that is a wrong interpretation we did not want to trigger.\n\n\"If you are a developer of a script that uses whatchanged, then\nrewrite it with 'log --raw --no-merges' and be happy.  If the script\nis very widely used, dropping us a note would be nice, as we can\nredirect end-user inquiries of your script towards you.  If you are\nan end-user of such a script, bug your supplier of such a script.\nThanks.\"\n\nperhaps?\n\n"},{"id":"524569","messageId":"3d919d08-4919-47a0-9583-d029f377a035@app.fastmail.com","threadId":"63990","inReplyTo":"xmqqsehl8zt8.fsf@gitster.g","subject":"Re: git whatchanged","fromName":"Kristoffer Haugsbakk","fromEmail":"kristofferhaugsbakk@fastmail.com","sentAt":"2025-08-20T21:11:53Z","receivedAt":"2025-08-20T21:12:16Z","isPatch":false,"sender":{"key":"kristofferhaugsbakk@fastmail.com","avatar":null},"body":"On Wed, Aug 20, 2025, at 23:10, Junio C Hamano wrote:\n> \"Kristoffer Haugsbakk\" <kristofferhaugsbakk@fastmail.com> writes:\n>\n>> The message itself reads like it could be read like: tell us and we\n>> might put the brakes on removing it (and that’s it).\n>\n> Yeah, that is a wrong interpretation we did not want to trigger.\n>\n> \"If you are a developer of a script that uses whatchanged, then\n> rewrite it with 'log --raw --no-merges' and be happy.  If the script\n> is very widely used, dropping us a note would be nice, as we can\n> redirect end-user inquiries of your script towards you.  If you are\n> an end-user of such a script, bug your supplier of such a script.\n> Thanks.\"\n>\n> perhaps?\n\nThat looks like it covers all the bases.  Great.\n\n-- \nKristoffer Haugsbakk\n"}]}