X-Recipient: archive-cygwin@delorie.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:message-id:from:to:references:in-reply-to
	:subject:date:mime-version:content-type
	:content-transfer-encoding; q=dns; s=default; b=JW/s5HoJG26HTecY
	mxnRWajSBo0QeBsTDgcjgRhHk/54/N+H+1Z7cv0yEmMAkyFRAagD/L5cRqicf+9W
	URyhc6GpHzDO7wRT8ZolSnK6zGv80ssFIRahDVVja+dltylhIPgZTJIsNzAuO294
	QnTzdGfLMpK8Mvo7HZi4AOKUOME=
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:message-id:from:to:references:in-reply-to
	:subject:date:mime-version:content-type
	:content-transfer-encoding; s=default; bh=LQwwSpaK06j3TgwrRjbPZ+
	K1R88=; b=Uj//GQkNhg7KPI7D7aTXHp2nybYQPp7XMzOa0TT4ZUSC6ihasH4oUC
	yaBMi9S7GZYw82+6HEtGBzb8q+gYxqk8evMvyKKlVoV935LZAaziAyF2GodvumA0
	lSDg/H+M+jpk+IK9Pl3O31AVIN3Lm58IcpWl0+RO7a4dIrsqXgLCc=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=-0.3 required=5.0 tests=AWL,BAYES_20,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,RP_MATCHES_RCVD,SPF_PASS autolearn=ham version=3.3.2
X-HELO: BLU004-OMC1S32.hotmail.com
X-TMN: [+Xau5PD22T3DDNdJblU5o/w4nHkaWTPm]
Message-ID: <BLU182-DS3FA926E18C37A612F5D99D4420@phx.gbl>
From: "Walter L." <bournenoir@hotmail.com>
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>
In-Reply-To: <56057078.3080907@cornell.edu>
Subject: Re: Issues encountered with new Cygwin version
Date: Fri, 25 Sep 2015 14:01:01 -0400
MIME-Version: 1.0
Content-Type: text/plain;	format=flowed;	charset="utf-8";	reply-type=original
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes

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.

Regards,
~WL 


--
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

