{"thread":{"id":"64148","subject":"Usage of git whatchanged","startedAt":"2025-09-14T12:48:25Z","lastAt":"2025-09-14T19:44:26Z","messageCount":4,"participants":["Bjoern Bastian","Kristoffer Haugsbakk"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"526273","messageId":"aMa5kSQVlhVX7Iii@eismeer","threadId":"64148","inReplyTo":null,"subject":"Usage of git whatchanged","fromName":"Bjoern Bastian","fromEmail":"bjoernbastian@posteo.de","sentAt":"2025-09-14T12:48:18Z","receivedAt":"2025-09-14T12:48:25Z","isPatch":false,"sender":{"key":"bjoernbastian@posteo.de","avatar":null},"body":"Hello,\n\nI still use 'git whatchanged' that has been available for a long time\nand though being longer than 'git log --raw' is much quicker to type,\nas 'git wh' is already sufficient for syntax completion. Obviously,\nfor this reason I won't use it with the '--i-still-use-this' option.\n\nBest regards,\nBjörn Bastian\n\n-- \nPhysicist\nWilhelm Ostwald Institute for Physical Chemistry, Leizig, Germany\n"},{"id":"526274","messageId":"7897d2d0-5564-4514-ab3b-7310b626f4c3@app.fastmail.com","threadId":"64148","inReplyTo":"aMa5kSQVlhVX7Iii@eismeer","subject":"Re: Usage of git whatchanged","fromName":"Kristoffer Haugsbakk","fromEmail":"kristofferhaugsbakk@fastmail.com","sentAt":"2025-09-14T13:10:20Z","receivedAt":"2025-09-14T13:10:47Z","isPatch":false,"sender":{"key":"kristofferhaugsbakk@fastmail.com","avatar":null},"body":"Hi\n\nOn Sun, Sep 14, 2025, at 14:48, Bjoern Bastian wrote:\n> I still use 'git whatchanged' that has been available for a long time\n> and though being longer than 'git log --raw' is much quicker to type,\n> as 'git wh' is already sufficient for syntax completion. Obviously,\n> for this reason I won't use it with the '--i-still-use-this' option.\n\n`git log --raw --no-merged` is the closest equivalent.\n\nWhat if you made a `wh` alias?\n\n    wh = log --raw --no-merged\n\n-- \nKristoffer Haugsbakk\n"},{"id":"526278","messageId":"8637f911-6887-41d5-b9af-cd2376376461@app.fastmail.com","threadId":"64148","inReplyTo":"aMbIqD4c5JY60fK1@eismeer","subject":"Re: Usage of git whatchanged","fromName":"Kristoffer Haugsbakk","fromEmail":"kristofferhaugsbakk@fastmail.com","sentAt":"2025-09-14T17:58:26Z","receivedAt":"2025-09-14T17:58:48Z","isPatch":false,"sender":{"key":"kristofferhaugsbakk@fastmail.com","avatar":null},"body":"On Sun, Sep 14, 2025, at 15:52, Bjoern Bastian wrote:\n> Hi Kristoffer,\n>\n> I simply followed the invitation printed upon `git whatchanged` to\n> join in giving feedback from those who frequently use the command.\n>\n> I did not expect a thoughtful reply, so thank you very much for it!\n>\n>> `git log --raw --no-merged` is the closest equivalent.\n>\n> Thanks for pointing this out, true (actually `--no-merges`).\n\nYep.\n\n>\n>> What if you made a `wh` alias?\n>>\n>>     wh = log --raw --no-merges\n>\n> Sure an alias will be the next obvious workaround. With bash I need to\n> include `git ` though and just type `wh` on the command line which is\n> okay. To get `git wh` I could maybe modify the bash completion.\n\nYou can also make a Git alias.\n\n    git config set --global alias.wh 'log --raw --no-merges'\n\n> One can live without, but the statement \"whatchanged is not even shorter\n> to type than log --raw.\" on https://git-scm.com/docs/git-whatchanged is\n> a weak one\n\nI have a proposal to remove it.\n\n> that misses obvious use cases of `whatchanged`.\n\nThe thing with git-whatchanged is that it uses the same underlying\nmachinery as git-log.  So there’s nothing that git-whatchanged can do\nthat git-log cannot do.\n\n... and I guess vice versa.  But historically git-log ended up as the\nnew-and-better replacement (according to the devs) with git-whatchanged\nbeing kept around for people who was used to typing it.\n\n-- \nKristoffer Haugsbakk\n"},{"id":"526284","messageId":"9bcd2f6e-8646-4b93-b2b2-fa1ccac5442b@app.fastmail.com","threadId":"64148","inReplyTo":"aMcYrG3XBZc9Yu_L@eismeer","subject":"Re: Usage of git whatchanged","fromName":"Kristoffer Haugsbakk","fromEmail":"kristofferhaugsbakk@fastmail.com","sentAt":"2025-09-14T19:44:05Z","receivedAt":"2025-09-14T19:44:26Z","isPatch":false,"sender":{"key":"kristofferhaugsbakk@fastmail.com","avatar":null},"body":"On Sun, Sep 14, 2025, at 21:34, Bjoern Bastian wrote:\n> Hi Kristoffer,\n>\n>> You can also make a Git alias.\n>>\n>>     git config set --global alias.wh 'log --raw --no-merges'\n>\n> neat, thank you, I never noticed the Git aliases.  I'll do that.\n>\n>> > One can live without, but the statement \"whatchanged is not even shorter\n>> > to type than log --raw.\" on https://git-scm.com/docs/git-whatchanged is\n>> > a weak one\n>>\n>> I have a proposal to remove it.\n>\n> Makes sense to me.\n>\n>> > that misses obvious use cases of `whatchanged`.\n>>\n>> The thing with git-whatchanged is that it uses the same underlying\n>> machinery as git-log.  So there’s nothing that git-whatchanged can do\n>> that git-log cannot do.\n>>\n>> ... and I guess vice versa.  But historically git-log ended up as the\n>> new-and-better replacement (according to the devs) with git-whatchanged\n>> being kept around for people who was used to typing it.\n>\n> Knowing Git aliases, there is actually no reason to keep `whatchanged`.\n> Without the idea to enforce `--i-still-use-this` in the transition time,\n> this would allow users to continue with their habits if they like to.\n\nSure, you can use something like that `wh` alias.\n\nBut note that you cannot make an alias like this named simply\n`whatchanged` (the same name as the command):\n\n    git config set --global alias.whatchanged 'log --raw --no-merges'\n\n(in order to continue with the same habits exactly, verbatim)\n\nBecause you cannot currently make an alias that has the same name as a\ncommand like this one.  But it looks like that restriction will be\nlifted for deprecated commands in a future version.\n"}]}