Abhijeet Sonar <abhijeet.nkt@xxxxxxxxx> writes:
> Currently, `git describe --dirty --broken` reports the working tree as
> dirty if you change the owner of a file. And as Phillip pointed out,
> calling `git update-index --unmerged -q --refresh` to update the index
> fixes this.
Starting from a clean state with a tracked file COPYING, I can do
this:
$ git describe --dirty --broken
v2.45.2-862-g39ba10deb2
$ cat COPYING >RENAMING && mv RENAMING COPYING
$ git diff-index --abbrev=8 HEAD
:100644 100644 536e5552 00000000 M COPYING
$ git describe --dirty --broken
v2.45.2-862-g39ba10deb2-dirty
$ git describe --dirty
v2.45.2-862-g39ba10deb2
This is with a version if Git _without_ your fix, i.e. the one whose
"describe --broken --dirty" does not do "git update-index --refresh".
In other words, the stat-only change to cause "diff-index" to report
a "suspected to be modified" does not have to be that the file is
owned by a different owner. So I still do not understand why you
want a second user in this test.
