DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:subject:to:references:from:message-id:date
	:mime-version:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=VEI1mDzHw9rFzjn0
	m98CuPsmAuIhNULi0014cnpAGQFS0ziQO3LNp7pipqGh/h4vnLwxiilI44xT6IBu
	H779S0KN3dTe23eoxIijLYvPxYT+7z0GcVVZi4Xkbjn2vWQy7hRtrDr7lLBOdDHp
	AquYojcPPrVV/J56pCFIu48K4WM=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Subject: Re: Issues encountered with new Cygwin version
To: cygwin@cygwin.com
References: <BLU182-W10FB6B21A2AEC90F71470FD4450@phx.gbl> <154887677.20150923111537@yandex.ru> <BLU182-DS2B4F831FEB7E4C1B67330D4440@phx.gbl> <56036256.8080209@tlinx.org> <BLU182-DS2567923242507AF88D9315D4430@phx.gbl> <56037F66.40209@tlinx.org> <BLU182-DS177F609D3B4BC69A880C77D4430@phx.gbl> <56042985.2040104@tlinx.org> <BLU182-DS23E73EC671521B950E6875D4420@phx.gbl>
From: Ken Brown <kbrown@cornell.edu>
Message-ID: <560566EA.3010503@cornell.edu>
Date: Fri, 25 Sep 2015 11:23:22 -0400
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.2.0
MIME-Version: 1.0
In-Reply-To: <BLU182-DS23E73EC671521B950E6875D4420@phx.gbl>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit

On 9/25/2015 11:01 AM, Walter L. wrote:
> On 24/09/2015 07:35, Marco Atzeri wrote:
>
>> > 2) The 'touch' command creates a file with the executable bit set
>> >
>> > [user@hostname ~]$ touch newfile.txt
>> > [user@hostname ~]$ ls -l newfile.txt
>> > -rwxrwx---+ 1 user Domain Users 0 Sep 22 17:21 newfile.txt
>>
>> It likely depends on the inherited permissions from the directory
>
> BINGO! Looks like starting 1.7.34 the file permissions were "fixed" to
> exhibit this new behavior
> (https://www.cygwin.com/ml/cygwin-announce/2015-02/msg00009.html). After
> reverting back to 1.7.33 I was able to get the previous behavior back.
>
> This is very unfortunate because I'm using Git in Cygwin specifically
> because it doesn't set the executable bit like Windows applications.
> With this new behavior, trying to rebase or cherry-pick causes merge
> conflicts because any file touched by Git will have the executable bit
> set. Additionally, trying to do a 'reset --hard' doesn't work anymore
> since the executable bit stays on with the new file permission behavior,
> so you'll never really return to the previous state.
>
> Yes, I can always set 'filemode=false' to ignore file permissions, but I
> still want to be able to enforce the correct file mode upon commits.
> Suggestions?

I think you misunderstood what Marco was saying.  If the problem is 
caused by the default ACL on the directory, you could fix that ACL.

Ken


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple