From: "Kristoffer Haugsbakk" <kristofferhaugsbakk@fastmail•com>
To: "Franz Brauße" <fb@paxle•org>
Cc: git@vger•kernel.org
Subject: Re: git whatchanged
Date: Fri, 07 Nov 2025 15:30:46 +0100 [thread overview]
Message-ID: <8883dc77-5894-4d9c-84d3-c29a434207d2@app.fastmail.com> (raw)
In-Reply-To: <20251107151620.2663adc25fec743cf1852d32@paxle.org>
On Fri, Nov 7, 2025, at 15:16, Franz Brauße wrote:
> On Fri, 07 Nov 2025 14:11:52 +0100 "Kristoffer Haugsbakk"
>>[snip]
>
> 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).
You can set up an alias with that name on Git 2.51.1 and 2.51.2 today.
(And later Git 2.52.0 (soon to be released).)
git config set --global alias.whatchanged 'log --raw --no-merges'
You cannot do that on Git 2.51.0 since you cannot alias builtin
commands. But you can alias deprecated builtin commands on
those versions.
> 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"
This is the current error message on Git 2.51.1 and later:
$ git whatchanged
'git whatchanged' is nominated for removal.
hint: You can replace 'git whatchanged <opts>' with:
hint: git log <opts> --raw --no-merges
hint: Or make an alias:
hint: git config set --global alias.whatchanged 'log --raw --no-merges'
If you still use this command, here's what you can do:
- read https://git-scm.com/docs/BreakingChanges.html
- check if anyone has discussed this on the mailing
list and if they came up with something that can
help you: https://lore.kernel.org/git/?q=git%20whatchanged
- send an email to <git@vger•kernel.org> to let us
know that you still use this command and were unable
to determine a suitable replacement
> for future deprecations [...] 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?
The thing about git-whatchanged(1) is that it has been deprecated for
twelve years according to the man page. But the man page didn’t
explicitly say “deprecated” in 2.51.0 and earlier. But that seems to
have been the intent. (Now it says explicitly that in the man page on
2.51.1 and later.)
This `--i-still-use-this` thing was only implemented (to the best of my
knowledge) for commands and functionality that have already been
deprecated for a long time. So it will not be used for fresh
deprecations.
>
> Anyhow, thanks again for all your work on this extremely nice tool!
next prev parent reply other threads:[~2025-11-07 14:31 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-07 11:40 git whatchanged Franz Brauße
2025-11-07 13:11 ` Kristoffer Haugsbakk
2025-11-07 14:16 ` Franz Brauße
2025-11-07 14:30 ` Kristoffer Haugsbakk [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-10-31 8:02 Remke Schuurmans
2025-10-31 8:23 ` Kristoffer Haugsbakk
[not found] ` <c2551c49-bcb4-4518-97d3-063941d591e8@gmail.com>
2025-10-31 9:13 ` Kristoffer Haugsbakk
2025-10-16 12:16 Julian Squires
2025-10-16 13:27 ` Kristoffer Haugsbakk
2025-10-13 12:44 Grzegorz Koperwas
2025-10-13 13:47 ` Kristoffer Haugsbakk
2025-10-08 14:20 Git whatchanged Filippo Falezza
2025-10-08 14:42 ` Kristoffer Haugsbakk
2025-10-02 6:48 git whatchanged Jiří Bašek
2025-10-02 7:12 ` Kristoffer Haugsbakk
2025-09-26 1:00 Neal Miller
2025-09-26 7:13 ` Kristoffer Haugsbakk
2025-09-26 15:54 ` Junio C Hamano
2025-09-28 1:12 ` Neal Miller
2025-09-10 20:49 Jose Jaramillo
2025-09-10 21:03 ` Kristoffer Haugsbakk
2025-09-10 21:15 ` Jose Jaramillo
2025-09-04 23:45 Michael Tourigny (TERAWE CORPORATION)
2025-09-03 15:34 Jesse Hathaway
2025-09-03 19:56 ` Junio C Hamano
2025-09-03 20:43 ` Kristoffer Haugsbakk
2025-09-03 21:47 ` Junio C Hamano
2025-08-26 13:04 Chris Palmer
2025-08-26 13:54 ` Kristoffer Haugsbakk
2025-08-19 17:51 Chris Judkins-Fisher
2025-08-19 17:59 ` Chris Judkins-Fisher
2025-08-19 20:57 ` rsbecker
2025-08-20 7:52 ` Kristoffer Haugsbakk
2025-08-20 14:12 ` rsbecker
2025-08-20 16:49 ` Junio C Hamano
2025-08-20 17:05 ` Chris Judkins-Fisher
2025-08-20 20:58 ` Kristoffer Haugsbakk
2025-08-20 21:10 ` Junio C Hamano
2025-08-20 21:11 ` Kristoffer Haugsbakk
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8883dc77-5894-4d9c-84d3-c29a434207d2@app.fastmail.com \
--to=kristofferhaugsbakk@fastmail$(echo .)com \
--cc=fb@paxle$(echo .)org \
--cc=git@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox