This is the mail archive of the
mailing list for the Cygwin project.
Re: Issues encountered with new Cygwin version
- From: "Walter L." <bournenoir at hotmail dot com>
- To: <cygwin at cygwin dot com>
- Date: Fri, 25 Sep 2015 14:01:01 -0400
- Subject: Re: Issues encountered with new Cygwin version
- Authentication-results: sourceware.org; auth=none
- References: <BLU182-W10FB6B21A2AEC90F71470FD4450 at phx dot gbl> <154887677 dot 20150923111537 at yandex dot ru> <BLU182-DS2B4F831FEB7E4C1B67330D4440 at phx dot gbl> <56036256 dot 8080209 at tlinx dot org> <BLU182-DS2567923242507AF88D9315D4430 at phx dot gbl> <56037F66 dot 40209 at tlinx dot org> <BLU182-DS177F609D3B4BC69A880C77D4430 at phx dot gbl> <56042985 dot 2040104 at tlinx dot org> <BLU182-DS23E73EC671521B950E6875D4420 at phx dot gbl> <560566EA dot 3010503 at cornell dot edu> <56057078 dot 3080907 at cornell dot edu>
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.
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple