On Wed, 2007-08-22 at 13:57, Erez Zadok wrote: > However, I noticed that after I copy a git repo (using v1.5.2.2), the index > entries are all out of sync, and I need to run git-reset. Why? What's in > the index file that changes after a cp -a or rsync that git depends on? Is > it atime's and if so, aren't they copied by cp -a or rsync? If it depends > on atime's, what happens if I mount my filesystem with noatime? Or does > git's index depends on inode numbers which change after a cp -a? (BTW, I > tried a variety of rsync options and none helped.) I also briefly looked at > the source code and wasn't able to find the answer. > > So, is there a way to efficiently copy a git repo on a local or remote host > w/o having to rerun git-reset afterwards? Use "git update-index --refresh" to update time stamps in the index. jdl - 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
