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

git-diff not showing changes (corrupt repo?)

From
DZDan Zwell <dzwell@gmail.com>
Date
Oct 2, 2007, 18:55 UTC
Message-ID
<47029414.3080100@gmail.com>

Hi, A small personal git repository has started lying to me about changed files. git-diff sometimes tells me that the index has no changes from HEAD, while other commands (git-status, at least) seem to tell the truth. It is the same after I commit the new changes--at that point, "git-diff-tree HEAD^ HEAD -p" spits out a nice patch, but "git-diff HEAD^ HEAD" gives nothing.

I have tried git versions 1.5.1.6-1.5.3.3, and they all act the same, so I think the repository is corrupt. Does sound familiar to anybody? If this is user error (for example, "git-reset --hard HEAD^" on a branch that had already been pulled into another branch), I can restore from a recent backup and redo some changes, but I would like to help troubleshoot this behavior if it is a git bug. Is this a known behavior? git-fsck doesn't reveal anything amiss, besides dangling objects. Does anybody know anything about this situation or what can cause it?

Example of behavior:

$ git status # On branch bak_linear-checks3 nothing to commit (working directory clean) $ echo "test" >> Makefile $ git status # On branch bak_linear-checks3 # Changed but not updated: # (use "git add <file>..." to update what will be committed) # # modified: Makefile # no changes added to commit (use "git add" and/or "git commit -a") $ git diff $

Thanks, Dan

Next: Junio C Hamano
Message 1 of 8 in “git-diff not showing changes (corrupt repo?)”
  1. Dan ZwellOct 2, 2007
  2. Junio C HamanoOct 2, 2007
  3. Dan ZwellOct 3, 2007
  4. Jeff KingOct 3, 2007
  5. Dan ZwellOct 3, 2007
  6. Jeff KingOct 3, 2007
  7. Linus TorvaldsOct 3, 2007
  8. Jeff KingOct 2, 2007

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.