threads / discuss / 64274

Git whatchanged

Subject: Git whatchanged

## tl;dr

2 messages between Oct 8, 2025 and Oct 8, 2025.

replies: 1people: 2as markdown or json

Filippo Falezza· Oct 8, 2025, 14:20 UTC · lore
To whom it may concern,

I am reaching out as I am still using the whatchanged option in git, which is very useful for my coding and handling merges. Please keep this option and do not break userspace.

Thank you kind regards

____________ Filippo Falezza

Kristoffer Haugsbakk· Oct 8, 2025, 14:42 UTC · re: Filippo Falezza · lore

Re: Git whatchanged

Good evening
On Wed, Oct 8, 2025, at 16:20, Filippo Falezza wrote:
> I am reaching out as I am still using the whatchanged option in git,
> which is very useful for my coding and handling merges.
> Please keep this option and do not break userspace.

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.

You can replace the command with `git log` thus:

• 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).

← back to recent threads