git/list[1] front-page[2] threads[3] people[4] search[5] about
 

query for recent changes that could lead to problems with gits index?

From
Heiko Voigt <hvoigt@hvoigt.net>
Date
Mar 2, 2010, 21:15 UTC
Message-ID
<20100302211518.GB37152@book.hvoigt.net>
Hi,

some of my users have recently experienced strange problems with the index since 1.7.0. It is msysgit on windows but seems to be more generic to me. Unfortunately we were not able to reproduce the failures.

Problem 1: User experiences strange behavior with staging files. I was puzzled until I found out that there was a double file entry in some recent trees. git ls-tree showed something like this:

... fileA ... fileB ... treeA ... treeA ... treeB ..

and git gc complained about it. There where non-ascii filenames involved in the changes.

Problem 2: Today a user asked me why a change he was only seeing in git blame marked as "working tree" does not show up in git gui nor gitk. A restart of both tools did not help. I took a brief look was puzzled and a 'git reset' resolved the issue. Unfortunately I did not take a look at the output of git status.

My question: Does anyone know recent changes (or situations) that could lead to such behavior?

cheers Heiko
Message 1 of 1 in “query for recent changes that could lead to problems with gits index?”
  1. Heiko VoigtMar 2, 2010

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.