Re: On refreshing the index

From: Junio C Hamano <gitster@pobox.com>
Date: Mar 13, 2010, 22:32 UTC
Message-ID: <7vmxyb3la7.fsf@alter.siamese.dyndns.org>
In-Reply-To: <loom.20100311T191149-453@post.gmane.org>

Sergio Callegari <sergio.callegari@gmail.com> writes:

Show 17 quoted lines

> If I run git status, git runs filters on a couple of opendocument files for
> which a filter is defined
>
> GIT_TRACE=1 git status
> trace: built-in: git 'status'
> trace: run_command: 'rezip -p ODF_UNCOMPRESS2'
> trace: exec: 'sh' '-c' 'rezip -p ODF_UNCOMPRESS2' 'rezip -p ODF_UNCOMPRESS2'
> trace: run_command: 'rezip -p ODF_UNCOMPRESS2'
> trace: exec: 'sh' '-c' 'rezip -p ODF_UNCOMPRESS2' 'rezip -p ODF_UNCOMPRESS2'
> # On branch M05
> # Untracked files:
> #   (use "git add <file>..." to include in what will be committed)
> #
> #       WIP/
> #       program.txt
> #       program.txt~
> nothing added to commit but untracked files present (use "git add" to track)

What does "git diff-files" and/or "git diff-index HEAD" say at this point? If they do not say there are no difference, that means that the file on the filesystem and the blob registered in the index are different, even though after transmogrified with rezip (whatever it does) these two different blobs may look the same.

"update-index --refresh" marks index entries for paths whose files on the filesystem are identical to the blobs registered for them in the index as up-to-date, so that later comparison do not have to inspect contents (instead, it can notice something has changed by looking at stat data such as file timestamps).

I think the difference between "may look the same" and "identical" is what you are seeing. Try "git add" on those paths and see what happens.