{"thread":{"id":"22885","subject":"query for recent changes that could lead to problems with gits index?","startedAt":"2010-03-02T21:15:19Z","lastAt":"2010-03-02T21:15:19Z","messageCount":1,"participants":["Heiko Voigt"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"136039","messageId":"20100302211518.GB37152@book.hvoigt.net","threadId":"22885","inReplyTo":null,"subject":"query for recent changes that could lead to problems with gits index?","fromName":"Heiko Voigt","fromEmail":"hvoigt@hvoigt.net","sentAt":"2010-03-02T21:15:19Z","receivedAt":"2010-03-02T21:15:19Z","isPatch":false,"sender":{"key":"hvoigt@hvoigt.net","avatar":"https://avatars.githubusercontent.com/u/184958?v=4"},"body":"Hi,\n\nsome of my users have recently experienced strange problems with the\nindex since 1.7.0. It is msysgit on windows but seems to be more generic\nto me. Unfortunately we were not able to reproduce the failures.\n\nProblem 1: User experiences strange behavior with staging files. I was\npuzzled until I found out that there was a double file entry in some\nrecent trees. git ls-tree showed something like this:\n\n... fileA\n... fileB\n... treeA\n... treeA\n... treeB\n..\n\nand git gc complained about it. There where non-ascii filenames involved\nin the changes.\n\nProblem 2: Today a user asked me why a change he was only seeing in git\nblame marked as \"working tree\" does not show up in git gui nor gitk.  A\nrestart of both tools did not help. I took a brief look was puzzled and\na 'git reset' resolved the issue. Unfortunately I did not take a look at\nthe output of git status.\n\nMy question: Does anyone know recent changes (or situations) that could\nlead to such behavior?\n\ncheers Heiko\n"}]}