Bernd Jendrissek <> writes:

> On Mon, Aug 13, 2012 at 5:02 PM, Thomas Rast <> wrote:
>> Can you share this repository?
> This weird behaviour doesn't even survive making a copy (cp -a) of the
> whole repository, so I very much doubt making it available would be
> illuminative. My disk's SMART data seems okay. The weird-quotient just
> rose a bit.

That sounds like an issue with stat() data, and then it doesn't.  cp -a
would change all the inode numbers, triggering a full refresh of the
index in 'git diff'.  But I'm not sure exactly how this can lead to
disagreement, since both commands read *both* index and worktree version
of the file.  Very confusing.

Can you try the following:

  git ls-files --debug 
  cp .git/index .git/index.orig
  touch gnetlist/tests/common/outputs/osmond/
  # note, it is important that you run diff first
  git diff gnetlist/tests/common/outputs/osmond/
  git diff-files -p gnetlist/tests/common/outputs/osmond/
  git ls-files --debug 

>> Or at least the pre- and post-change
>> files, transferred in such a way that there won't be any whitespace
>> damage (your snippets above show obvious damage).  You can use
> contains the output from git show a5ee1e7. Leave off the ?text for an
> application/octet-stream download.

Umm, that's only one side of the diff, isn't it?  The hunk header claims
that the hunk goes up to line 47, so there must be more changes beyond
what you showed.

Thomas Rast
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to
More majordomo info at

Reply via email to