Matthieu Moy venit, vidit, dixit 20.09.2010 11:56: > "Gaer, A." <Andreas.Gaer@xxxxxxxxxxxxx> writes: > >> On a copied source directory "git status" seems to be about >> 3 times slower than on the original directory. > > It is expected that the first "git status" be slower. It will most > likely have to actually re-diff the files and update the index > stat-cache. > > But I'm surprised that the next "git status" are still slow. Other > people may get a better explanation, but this very much looks like a > bug. In the OP's case, the inode/dev info differs (after copying, or after moving across FS boundaries). I don't think "git status" updates these. I noticed (and reported) something like this a while ago when, after a reboot, I would get warnings about crossing FS boundaries. Only a "rm .git/index && git reset --hard" was able to refresh the index properly. This case seems to be similar, although a simple "git reset --hard" appears to suffice. Michael -- 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