Re: git whatchanged -- yes, I still use this
- From
- Kristoffer Haugsbakk <kristofferhaugsbakk@fastmail.com>
- Date
- Oct 5, 2025, 10:31 UTC
- Message-ID
- <b3a8dd87-fdab-41cc-b221-b62aa7f74387@app.fastmail.com>
- In-Reply-To
- <CA+Hr9go-jyDeau8HVi+fUuiTTgAS_SNgyGL9x660+GzGJZJBEQ@mail.gmail.com>
On Sun, Oct 5, 2025, at 04:14, Jeffery Carr wrote:
> If you are going to remove it, "alias" it to something.
Git doesn’t have built-in aliases, if you mean Git aliases more literally. If not then it already acts as a sort of alias, I guess.
> alternatively, I guess I'll make "git-whatchanged" binary to do it.
This command is being removed because git-log(1) supplanted it over 12 years ago. Both commands use the same machinery, just with different defaults.
Here’s how to replace it with git-log(1):
• 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).
Show 6 quoted lines
> I'd also suggest, instead of the message: > >[snip] > add to the message: > > <run this instead>
This is coming in the next versions.