Johannes Schindelin <Johannes.Schindelin@xxxxxx> writes: > It could be possible that the index is saved in a slightly different > format, due to different alignment strategies. Maybe 64-bit vs 32-bit has > differences there. I have no idea. As far as I am aware of, there should be no such difference, although we probably rely on int being 32 and long being 64 bit. We do store our numbers in network byte order. However, did somebody say FAT-32? I seem to recall that that filesystem lacks uid/gid, so I am reasonably sure there would be different return values for the same path from lstat(2) between git on Cygwin/MinGW and on Linux that mounts the same filesystem using vfat driver with different uid= & gid= mount options. That difference which would make the paths stat-dirty. Also there is the problem of i-num we discussed lately. The i-num we get for the same path from lstat(2) can be different when same filesystem is mounted by different operating systems (remember that NTFS on Linux and Cygwin?). So even though file format of the index may be designed and implemented to be portable, it might not be practical to use the same physical repository from different OSes, depending on the combination of things. - 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