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: Sun, 27 Sep 2015 10:45:45 -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> <1275666051 dot 20150926120518 at yandex dot ru> <BLU182-DS1484E63B23E4228B1C49B4D4410 at phx dot gbl> <560717D5 dot 5010201 at cornell dot edu> <BLU182-DS1396F60CE885BBA6F983E3D4400 at phx dot gbl> <881548635 dot 20150927125434 at yandex dot ru>
On 9/27/2015 5:54 AM, Andrey Repin wrote:
Greetings, Walter L.!
My question was merely based on Andrey's statement that "This is
configurable" (see above); I don't know what he meant and what "this" is,
Git or Cygwin.
"This" being "Git", and http://cygwin.com/ml/cygwin/2015-09/msg00072.html
If by saying "This is configurable" he meant running 'setfacl -b' on the
top-level directory, then I simply misunderstood his statement; I was
just misinterpreting "configurable" meaning setting "noacl" or something
like that to the file system or the environment.
The problem child here is Git that bindly assumes that there's no other
permissions than POSIX permissions, and no other executables than POSIX
Both statements aren't true for any given OS these days.
Since there are usually more than one way to do something, I was just
wondering if Andrey knew of another way to handle the permission issue by
the way of some configuration setting.
I didn't, but I'm reading the list patiently, picking knowledge where I
Thanks to Adam. This solution came up relatively recently.
Thanks for the clarification and the link, Andrey; it certainly gives me a
better picture of what's going on. Unfortunately, per my previous email,
configuring Git with "core.fileMode=false" won't help me because I still
want to enforce file permissions and not ignore it. Other developers
sometimes inadvertently set the wrong permission on some files and I want to
be able to revert them to the correct permission upon my next commit of the
Calling 'setfacl -b' on the parent folder containing the project suggested
by Ken may be the best course of action until Git changes its behavior.
Thanks again to both of you for the depth of information provided.
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple