From: Junio C Hamano <gitster@pobox.com>
Date: Thu, 22 May 2008 09:04:09 GMT
Subject: Re: [PATCH] Fix t6031 on filesystems without working exec bit
Message-ID: <7vskwawvzq.fsf@gitster.siamese.dyndns.org>
In-Reply-To: <81b0412b0805220116h4e4ff279k2e433a8a9a1cd9fc@mail.gmail.com>

"Alex Riesen" <raa.lkml@gmail.com> writes:

> 2008/5/21 Junio C Hamano <gitster@pobox.com>:
> ...
>> @@ -12,6 +15,7 @@ test_expect_success 'mode change in one branch: keep changed version' '
>>        git add dummy &&
>>        git commit -m a &&
>>        git checkout -b b1 master &&
>> +      chmod +x file1 &&
>>  	  git update-index --chmod=+x file1 &&
>
> Now, this is pointless in my setup. Cygwin just ignores the operation
> and decidedddds (presumably according the file _content_ or maybe
> phase of the moon) that is not executable. Working tree is still modified.

Doesn't it mean you spotted a bug?

If your repository is marked so that executable bit is untrustworthy
there, the check done when switching to branch "a1" to compare if "file1"
that is involved in the switch operation has local changes should ignore
(apparent and false) executable-bit change, shouldn't it?