Hi Keith, On Fri, 2 Feb 2018, Keith Goldfarb wrote: > > The purpose of these values is to allow to notice a change on the file > > system without going through the actual file data. Duplicating > > st_mtime would be pointless. > > Well, I agree with the first statement. I disagree with the 2nd. It’s > not pointless to fix a problem, and in theory the creation date of a > file can never change. > > > Don't do that then. Use core.trustctime. > > I am. Unfortunately, my problem isn’t solved by that alone. Perhaps this > deserves its own thread, but on Windows the st_ino field is set to zero. > This can also trigger a false positive, causing the whole cache to be > rebuilt unnecessarily. You cannot assume that the inode numbers are identical between file systems/operating systems. That's simply not going to work. I know you really want *so hard* for the same working directory to be accessible from both Windows and Linux. I have a lot of sympathy for that sentiment. Though I do not see much chance for success on that front. Ciao, Johannes
