On Thu, Jan 19, 2006 at 11:12:27PM +0100, Alex Riesen wrote: >Christopher Faylor, Thu, Jan 19, 2006 19:28:22 +0100: >>>>By the way, if you have an access to git on cygwin with FAT, could you >>>>test your patch ($SECONDS) and then i-num patch (the machine with >>>>cygwin I can borrow has only NTFS) please? >>> >>>Works if sleep is for 2 secs (I completely forgot about that stupid FAT >>>granularity!) st_ino is always the same (it is a hash of pathname). >>>Christopher, how is that supposed to work with hardlinks? (NTFS has >>>hardlinks, BTW) >> >>There is OS support hardlinks work on NTFS/NT but not on FAT* >>"filesystems" or Windows 9x variants. Hardlink support on Cygwin >>mirrors this. > >No, I rephrase the question: how does the method of calculating .st_ino >from pathname handles hardlinked files on NTFS? By briefly looking at >the code it does not seem to be possible. Cygwin doesn't create an inode from the path name on NTFS. NT gives you a 64 bit unique number which identifies a file so we use that. That means that the inodes of hardlinked files should be the same, just like on linux. Inodes are only calculated by hashing the path name when the OS lacks the support to provide a "real" inode and in that case there is no hard link support available so it's a non-issue. cgf - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.htmlReceived on Fri Jan 20 09:27:06 2006
This archive was generated by hypermail 2.1.8 : 2006-01-20 09:27:13 EST