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=WbmA+zbm8UwwhNwY
	5oIzBllvXri5qpvh0IKVCi4UXtAzDq1u6U1PRI91m2ESP2U79DpJYS6Z0u9nsypf
	dEQLpV1hDwa2yK1QmzxFSxVXNEa6q2uFMP7gjVW5l5XjS1xPZ+Ukqr/qcluOwdwA
	hSyaMHYQnhfCDvaH1X1zY+/uEZE=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Message-ID: <BLU182-DS10E40C170599E2C6841310D4400@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>  <1275666051.20150926120518@yandex.ru>  <BLU182-DS1484E63B23E4228B1C49B4D4410@phx.gbl> <560717D5.5010201@cornell.edu>  <BLU182-DS1396F60CE885BBA6F983E3D4400@phx.gbl> <881548635.20150927125434@yandex.ru>
In-Reply-To: <881548635.20150927125434@yandex.ru>
Subject: Re: Issues encountered with new Cygwin version
Date: Sun, 27 Sep 2015 10:45:45 -0400
MIME-Version: 1.0
Content-Type: text/plain;	format=flowed;	charset="utf-8";	reply-type=original
Content-Transfer-Encoding: 7bit

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
> executables.
> 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
> can.
> 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
files.

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.

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