Am 13.06.22 um 19:29 schrieb Junio C Hamano: > Johannes Sixt <j6t@xxxxxxxx> writes: > >> git status does not compute differences; it only looks at the stat >> information, and that is by design for performance reasons. So, IMO, >> this is working as designed and not a bug. > > Hmph, is that true? I thought "git status" did an equivalent of > diff.autoRefreshIndex just like other commands like "git diff" at > the Porcelain level. Is it true? I don't know; you tell me ;) git status certainly does autoRefreshIndex, but is that based on a diff computation? I thought git status looks only at stat information. > Is this more like the commonly seen "after you futzed the attributes > to affect normalization, "--renormalize" is needed to force the > index to match the cleaned version of working tree under the new > clean filter rules", I wonder? Not in this case. The modified file that git status reports happens long after git commit -a has already applied the new filter. -- Hannes
