Re: [PATCH] git-init: don't base core.filemode on the ability to chmod.
- From
- Jan Hudec <bulb@ucw.cz>
- Date
- Oct 10, 2007, 09:47 UTC
- Message-ID
- <20071010094704.GA7865@efreet.light.src>
- In-Reply-To
- <20071004084237.GE20800@admingilde.org>
On Thu, Oct 04, 2007 at 10:42:37 +0200, Martin Waitz wrote:
Show 15 quoted lines
> hoi :) > > On Thu, Oct 04, 2007 at 01:21:02AM -0700, Junio C Hamano wrote: > > FWIW, I did not mean it to be an example for preferred > > indentation nor code layout, but as a better way to explain what > > the logic is computing. > > sure, and I think it makes sense the way you wrote it. > > > I do not think git on Cygwin nor WinGit creates $GIT_DIR/config > > with executable bit set. Is this pretty much a workaround only > > for vfat-on-Linux ? > > I just checked Cygwin, it creates files without executable bit and > disregards a chmod +x. So yes, this seems to be a Linux-only problem.
AFAIR in cygwin it depends on both configuration of cygwin and whether you are on NTFS or FAT. On NTFS with proper setting (CYGWIN=ntsec IIRC), cygwin actually implements the x bit (uses the NT ACL to somewhat represent it). On other filesystem there is an option somewhere to tell whether it should show the x bit always set or always cleared (for me it seems to be always set).
On the other hand MSYS shows the x bit as set whenever the file has executable extension. I don't think cygwin has this mode.
-- Jan 'Bulb' Hudec <bulb@ucw.cz>