Re: [PATCH] describe: refresh the index when 'broken' flag is used
From: Abhijeet Sonar <hidden>
Date: 2024-06-25 06:40:56
Possibly related (same subject, not in this thread)
- 2024-06-25 · Re: [PATCH] describe: refresh the index when 'broken' flag is used · Karthik Nayak <hidden>
- 2024-06-24 · Re: [PATCH] describe: refresh the index when 'broken' flag is used · Abhijeet Sonar <hidden>
- 2024-06-24 · Re: [PATCH] describe: refresh the index when 'broken' flag is used · Junio C Hamano <hidden>
- 2024-06-24 · Re: [PATCH] describe: refresh the index when 'broken' flag is used · Abhijeet Sonar <hidden>
- 2024-06-24 · Re: [PATCH] describe: refresh the index when 'broken' flag is used · Abhijeet Sonar <hidden>
> So I still do not understand why you > want a second user in this test. What I really wanted to do was closely mirror the environment in reproduction steps mentioned in original bug report. Which I figured could be done by changing the owner to a second user. On 24/06/24 23:28, Junio C Hamano wrote:
$ 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-g39ba10deb2Thanks, I will use this in the tests.