Re: Seeing various mode changes on cygwin

From: Junio C Hamano <junkio@cox.net>
Date: Oct 10, 2005, 07:38 UTC
Message-ID: <7vu0fpbz43.fsf@assigned-by-dhcp.cox.net>
In-Reply-To: <Pine.LNX.4.63.0510100220330.23242@iabervon.org>

Daniel Barkalow <barkalow@iabervon.org> writes:

Show 5 quoted lines

> Perhaps have a bit in the index mode for the file to say that the mode in 
> the filesystem is unreliable, which gets set if a stat of the 
> newly-written file doesn't match the mode it was supposed to have, or if 
> git chmod is used to change it; then, if the bit is set, ignore the mode 
> in the filesystem and just use the mode in the index.

In effect, you are making the "per-repo configuration" Linus mentioned a non configuration but a property recorded in the index file. I think this is a clever solution which is very helpful to the end user. I have to think about this a bit, but my gut feeling tells me that it is the right direction if it works.

I do not think you have to necessarily record it in the "index mode" -- which implies this is per path -- nor even in the index file itself. We might even be able to get away with doing this check at git-init-db time just once, and record it in a file, say ".git/fs-mode-unreliable".