Re: git whatchanged

From: Franz Brauße <fb@paxle.org>
Date: Nov 7, 2025, 14:16 UTC
Message-ID: <20251107151620.2663adc25fec743cf1852d32@paxle.org>
In-Reply-To: <671d53bd-952f-4849-9e5e-910e49d4c4e4@app.fastmail.com>

On Fri, 07 Nov 2025 14:11:52 +0100 "Kristoffer Haugsbakk" <kristofferhaugsbakk@fastmail.com> wrote:

Show 7 quoted lines

> 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.
> 
> You can replace it with `git log` in this way:
> [snip]
> See: https://git-scm.com/docs/BreakingChanges

Thank you for the additional infos and the link, I didn't know that! I suppose when it's being removed, I can resurrect the "whatchanged" subcommand via the config's alias mechanism (git wh<TAB> is just baked into my fingers at the moment).

Might I suggest that for future deprecations instead of an annoying to type flag just a message like "this command is scheduled for removal in v<VERSION>, see <URL>; use "git log --raw --no-merges" for similar functionality" is printed in addition to the command still working as before while it's there? Similar to how "git pull" informs users about the rebase vs. merge options in case of diverged branches?

Anyhow, thanks again for all your work on this extremely nice tool!

Franz