Checking out messes up execution bit

Checking out messes up execution bit

[Manuel Strehl]

Hello list,

I asked a question over at superuser.com about git checkouts messing up 
the execution bit of freshly committed files:

http://superuser.com/questions/204757

To put it in a nutshell: I edit and commit a file in branch "master", 
then I check out branch "dev" and the edited file gets the execution bit 
set. This leads to a working copy differing from the content of the 
index. It's especially painful when I try to merge "master" into "dev", 
which fails then. I'm working under ext4 and Samba/CIFS, respectively.

One answerer at superuser thinks that this looks like a bug in git 
itself. Therefore I'd like to check with you, if there is possibly 
another explanation for my observation, before I issue a bug report.

Best,
Manuel

Re: Checking out messes up execution bit

[Peter Harris]

On Sat, Nov 6, 2010 at 5:11 PM, Manuel Strehl wrote:
> To put it in a nutshell: I edit and commit a file in branch "master", then I
> check out branch "dev" and the edited file gets the execution bit set. This
> leads to a working copy differing from the content of the index. It's
> especially painful when I try to merge "master" into "dev", which fails
> then. I'm working under ext4 and Samba/CIFS, respectively.

This is because CIFS does not support the execution bit.

> One answerer at superuser thinks that this looks like a bug in git itself.
> Therefore I'd like to check with you, if there is possibly another
> explanation for my observation, before I issue a bug report.

See core.fileMode in "git help config"

Peter Harris