Re: git fast-export not preserving executable permissions?

From: Johannes Schindelin <johannes.schindelin@gmx.de>
Date: May 4, 2020, 14:23 UTC
Message-ID: <nycvar.QRO.7.76.6.2005041620540.56@tvgsbejvaqbjf.bet>
In-Reply-To: <20200501223240.GG41612@syl.local>

Hi,

On Fri, 1 May 2020, Taylor Blau wrote:

> If you are using NTFS or FAT32, neither of these filesystems support
> execute permission bits. (I am certainly not an expert here, but I know
> that Dscho (cc'd) would be able to answer authoritatively here.)

On Windows, there are indeed no executable bits. A file is considered executable if it has a file extension indicating it, e.g. `.exe`.

In Git for Windows' Bash (which comes from MSYS2), `ls -l` will also consider files whose first line is a hash-bang one (e.g. `#!/bin/sh`) as executable. This information is however _not_ used by Git.

If you want to mark a file as executable in Git for Windows, you will have to use `git add --chmod=+x <file>`.

Ciao, Johannes