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

Re: git-diff not showing changes (corrupt repo?)

From
Junio C Hamano <gitster@pobox.com>
Date
Oct 2, 2007, 19:15 UTC
Message-ID
<7vbqbhl44h.fsf@gitster.siamese.dyndns.org>
In-Reply-To
<47029414.3080100@gmail.com>
Dan Zwell <dzwell@gmail.com> writes:
> ... 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.

This part is most interesting. They are both about comparing two commits and do not interact with anything in the work tree nor your index.

> I have tried git versions 1.5.1.6-1.5.3.3, and they all act the same,
Do you mean 1.5.1.5 was Ok?  Can you bisect it?
> so I think the repository is corrupt. Does sound familiar to anybody?

Not to me; and I do not think repository is corrupt from the two "HEAD^ vs HEAD" diff. There is something entirely different going on.

> ... 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.
Thanks.
Previous: Dan ZwellNext: Dan Zwell
Message 2 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.