Michael J Gruber <git@xxxxxxxxxxxxxxxxxxxx> writes:
> This happens whenever the "stat" information changes, e.g. due to
> changed device numbering and such. "git reset --hard" would have been
> the quickiest way to reset the stat cache/index - after git diff, of
> course ;)
That does not quite explain why 'git status' reported modified files
in the first place. It would have refreshed the cached stat info in
the index as the first thing to do. "git status" I think is the
recommended way these days ("update-index --refresh" for us old
timers) to nondestructively correct the cached stat information
discrepancy caused by "cp -R".
If you need to resort to "reset --hard", then there is something
else going on.
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html