Hello, I still use git whatchanged. Thank you. Samer
Re: I still use git whatchanged
On Mon, Oct 13, 2025, at 23:59, Samer Abdallah wrote:
> I still use git whatchanged.
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).
Junio C HamanoRe: I still use git whatchanged
"Kristoffer Haugsbakk" <kristofferhaugsbakk@fastmail.com> writes:
Show 11 quoted lines
> On Mon, Oct 13, 2025, at 23:59, Samer Abdallah wrote: >> I still use git whatchanged. > > 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).
Thanks for fielding these repeated questions.
Let's do a maintenance release Git 2.51.1 very soon with your kh/you-still-use-whatchanged-fix topic, together with other minor documentation changes and probably a hdnful of ci related fixes.
We haven't had non-security maintenance releases for quite a while, so I may need to remember and practice the procedure to cut one ;-)
Re: I still use git whatchanged
On Tue, Oct 14, 2025, at 01:01, Samer Abdallah wrote:
Show 10 quoted lines
> Hi Kristoffer, > > Thank you for your reply. > I should have added that I use it to see the history of changes for the current > file I’m editing, using the `-p` option and a file name argument, (and binding > it to the command `:Ghist` in vim.) > > However, the following seems to produce the same output, as you suggested > > git log -p --no-merges —raw <filename>
Good. That’s great.