X-Recipient: archive-cygwin AT delorie DOT com 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= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; 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; s=default; bh=hPWYONSfbocHVson6ypkSl 5aRqA=; b=kkWZ26LfLc9JAYvT9oslbf9+RQ+NvCw4q12TmnuAcRQs8nklo3O2H2 uwY655uF33oTMMM5jH7jIQRpXEZ98gB6vPLUo0UuOwbiZvQ8LFjyfQAXTlHgekJF DNLi+NM8WA7n23rTt6xH+5BWh0lN53i0+xveJ863H/ebGtC2zkBcc= Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=AWL,BAYES_00,RP_MATCHES_RCVD,SPF_HELO_PASS,SPF_PASS autolearn=ham version=3.3.2 X-HELO: limerock02.mail.cornell.edu X-CornellRouted: This message has been Routed already. Subject: Re: Issues encountered with new Cygwin version To: cygwin AT cygwin DOT com References: <154887677 DOT 20150923111537 AT yandex DOT ru> <56036256 DOT 8080209 AT tlinx DOT org> <56037F66 DOT 40209 AT tlinx DOT org> <56042985 DOT 2040104 AT tlinx DOT org> <560566EA DOT 3010503 AT cornell DOT edu> <56057078 DOT 3080907 AT cornell DOT edu> From: Ken Brown 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: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes 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