Gaer, A. venit, vidit, dixit 20.09.2010 11:20: > Hello all, > > while moving a project directory around I stumbled over an interesting > phenomenon. On a copied source directory "git status" seems to be about > 3 times slower than on the original directory. Only after a "git reset" > both copies behave the same again. Is this connected to the timestamps > of files & directories? Actually I would like to move the project > directories of several software developers to a new partition and > forcing them all to "git reset" in all of their repos is a little bit > annoying. Any suggestions how to "repair" the repos less intrusive? > Since you clone from A to B, then copy from B several times, why don't you clone from A several times instead? If it's really about moving across file-system boundaries, then I don't think there's a way around: you need to refresh the index with the changed inodes information. 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