Re: Gitk/Cygwin bug: phony local changes
- From
- Hannu Koivisto <azure@iki.fi>
- Date
- Oct 28, 2008, 16:04 UTC
- Message-ID
- <831vy03dui.fsf@kalahari.s2.org>
- In-Reply-To
- <81b0412b0810280827o2ccca3bfw127877782f5a0909@mail.gmail.com>
"Alex Riesen" <raa.lkml@gmail.com> writes:
Show 16 quoted lines
> 2008/10/28 Hannu Koivisto <azure@iki.fi>: > >> I used bisect to find which commit introduced this bug and the >> result is: >> >> 7faee6b8de836904227ee98dc3d2c4c75b0ef3a1 is first bad commit >> commit 7faee6b8de836904227ee98dc3d2c4c75b0ef3a1 >> Author: Mark Levedahl <mlevedahl@gmail.com> >> Date: Mon Oct 13 00:33:31 2008 -0400 >> >> compat/cygwin.c - Use cygwin's stat if core.filemode == true >> > > Could you try the patch from Junio's "Re: [PATCH] Only update the > cygwin-related configuration during state auto-setup" mail and see > if it changes anything?
It seems to fix the problem.
Something I forgot to mention in the previous mail: the problem occurs whether I have core.fileMode set to true or false.
-- Hannu