AW: git performance after directory copy

Hello all,

thanks Matthieu for your tip. "git diff" without "autorefreshindex" shows that all files have different stat info. Calling "git update-index --refresh" seems to be the right cure.

What I find a little bit confusing is that "git status" does not warn about such a situation, or even "repair" it. As I said, I wanted to move the project directories of several developers to a new partition without too much interference and the first try didn't succeed because people complained about "bad" "git status" performance (people get used to git rocket-fast performance very soon ;-).

Maybe this was introduced in the 1.7 release: "git status" is not "git commit --dry-run" anymore. "git commit --dry-run" does behave as you expect: first call takes a little bit longer, subsequent calls are fast again.

BTW, I tested on a system with git version 1.7.1 installed, but release notes do not suggest any changes in that respect in 1.7.2 or 1.7.3.

Regards,
 Andreas.