Hello, Nice to meet you,
I would like to say that I still use `git whatchanged` I like the way we see the modified files instead of just `git log` And actually I never saw the message before today when I showed the command to a friend of mine, will it be removed soon ? Is there any alternatives that are straight to the point without any args or something?
In any cases, thanks for your amazing work,
Best regards Antoine Cousson
Re: git whatchanged --i-still-use-it
Good evening
On Tue, Mar 3, 2026, at 17:01, Antoine Cousson wrote:
> I would like to say that I still use `git whatchanged` I like the way > we see the modified files instead of just `git log`
This command is being removed because it was supplanted by git-log(1) a long while ago. Both commands use the same machinery, just with different defaults.
> And actually I never saw the message before today when I showed the > command to a friend of mine, will it be removed soon ?
It is planned for removal in Git 3.0. There is no plan for when Git 3.0 will be released.
See: https://git-scm.com/docs/BreakingChanges
> Is there any alternatives that are straight to the point without any > args or something?
You can replace it with `git log` in this way:
• Given: `git whatchanged <opts>` • Replace with: `git log <opts> --no-merges --raw`
Additionally for the sake of readability, you might have more use for `--stat` or `--name-only` rather than `--raw` if you are only reading the output (not feeding the output to another program).
You can also use `--patch` to see the full diffs.
> > In any cases, thanks for your amazing work, >[snip]
Junio C HamanoRe: git whatchanged --i-still-use-it
Antoine Cousson <antoine.cousson@protonmail.com> writes:
> I would like to say that I still use `git whatchanged` I like the way we see the > modified files instead of just `git log`
Then perhaps you would like "git log --stat" even better? Instead of meaningless pair of hexadecimal object names, you'd get a sense of the size of damage each commit causes to the codebase.
The command is going away. You could
$ git config alias.whatchanged "log --raw --no-merges"
if you really prefer the ugly hexadecimal gibberish, though.
Re: git whatchanged --i-still-use-it
On Tue, Mar 3, 2026, at 19:03, Junio C Hamano wrote:
>[snip] > The command is going away. You could > > $ git config alias.whatchanged "log --raw --no-merges" > > if you really prefer the ugly hexadecimal gibberish, though.
Yes, on Git v2.51.1, Git 2.52 or higher.
Re: git whatchanged --i-still-use-it
> Then perhaps you would like "git log --stat" even better? Instead
of meaningless pair of hexadecimal object names, you'd get a sense of the size of damage each commit causes to the codebase.
I have tested "git log --stat" and I really liked the display, thanks for the tips
I agree that i was not looking at the hexadecimal but more to the names of the file, the visual representation og the changes and the numbers are great !
> Yes, on Git v2.51.1, Git 2.52 or higher.
I am on v2.43.0 I will update thanks
Le mardi 3 mars 2026 à 7:17 PM, Kristoffer Haugsbakk <kristofferhaugsbakk@fastmail.com> a écrit :
> On Tue, Mar 3, 2026, at 19:03, Junio C Hamano wrote: > >[snip] > > The command is going away. You could > > > > $ git config alias.whatchanged "log --raw --no-merges" > > > > if you really prefer the ugly hexadecimal gibberish, though. >
> Yes, on Git v2.51.1, Git 2.52 or higher. >
Re: git whatchanged --i-still-use-it
Have a nice evening regards
Antoine
Envoyé avec un e-mail sécurisé Proton Mail.
Le mardi 3 mars 2026 à 8:56 PM, Antoine Cousson <antoine.cousson@protonmail.com> a écrit :
> > Then perhaps you would like "git log --stat" even better? Instead > of meaningless pair of hexadecimal object names, you'd get a sense > of the size of damage each commit causes to the codebase. >
> I have tested "git log --stat" and I really liked the display, thanks for the tips > I agree that i was not looking at the hexadecimal but more to the names of the file, the visual representation og the changes and the numbers are great ! >
>
> > Yes, on Git v2.51.1, Git 2.52 or higher. >
> I am on v2.43.0 I will update thanks >
>
>
> Le mardi 3 mars 2026 à 7:17 PM, Kristoffer Haugsbakk <kristofferhaugsbakk@fastmail.com> a écrit : >
> > On Tue, Mar 3, 2026, at 19:03, Junio C Hamano wrote: > > >[snip] > > > The command is going away. You could > > > > > > $ git config alias.whatchanged "log --raw --no-merges" > > > > > > if you really prefer the ugly hexadecimal gibberish, though. > > > > Yes, on Git v2.51.1, Git 2.52 or higher. > >