Am 28.09.22 um 11:02 schrieb Tim Jaacks: > >> Letting `git diff X^!` mean the same as `git diff X ^X^` for a >> non-merge makes sense to me given the definition from >> gitrevisions(7) cited above. That in turn is the same as `git diff >> X^..X` and `git diff X^ X`. > > Yes, that is exactly how it worked before. And all the other syntaxes > still work correctly. `git diff X^!` still works for a non-merge commit as well. Only merge commits were affected by the change made in v2.28. And stashes are stored as merge commits internally, causing them to be affected. > René, I saw you submitted some patches already, but these weren't > approved obviously. So how does this continue now? It's RC time (release candidate) and only fixes for regressions added after v2.37 are accepted currently. I'll resend my patches once v2.38 is out, if necessary. René
