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=ylBdotYn81IQXYOx
	ZDKOVaDz8B40iYFb1vCdicNph354OS6dDWwHnImbLlTZNpa5y027NLDjh9fpat0l
	kvAWVsUAjmm1pXF782Pn5yAROCnt5GrRsCUDEgU6qunwCxxvvGbvEImadvXcGiC7
	ZLNNXEDVz9ZjraDVWVItiFp8Un8=
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> <560566EA.3010503@cornell.edu> <56057078.3080907@cornell.edu> <BLU182-DS3FA926E18C37A612F5D99D4420@phx.gbl>
From: Ken Brown <kbrown@cornell.edu>
Message-ID: <5605917A.5090706@cornell.edu>
Date: Fri, 25 Sep 2015 14:24:58 -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-DS3FA926E18C37A612F5D99D4420@phx.gbl>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit

On 9/25/2015 2:01 PM, Walter L. wrote:
> On 9/25/2015 12:04 PM, Ken Brown wrote:
>
>> > 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.
>>
>> To elaborate on this, observe the following:
>
> Hi Ken, thanks for the clarification. I understood what Marco meant and
> your
> examples. I was just saying that the new (correct?) behavior of inheriting
> the ACL from the parent folder for newly created file has the side
> effect of
> causing Git to behave differently from before.
>
> I suppose the point you're making (based on your example) is that I should
> just remove the ACL from the parent folder if I don't want new files in the
> folder to inherit the executable bit. If that's the case then I guess I'll
> need to do that anytime I clone a new project.

Why not just run 'setfacl -b' once and for all on whatever directory you 
do your work in?  Is it under your home directory?  Do you have default 
ACL entries on your home directory that are then inherited by every 
subdirectory you create?

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