DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:reply-to:message-id:to:subject
	:in-reply-to:references:mime-version:content-type
	:content-transfer-encoding; q=dns; s=default; b=Ebb3jh/fvI8TFus1
	WnQHEJMku4a0xeUVzGs9Jz7xW3zOaSIPru8bco9Ha5Sz2VrWtPwN6vtxCEwixPoa
	P5XWhO3THGcoGw9FSlUGhCjoI0pG8Gdq8EdwV/A7+ul0FzIBFLAn5sTizK2nuDWL
	D3Dp4T06GpkjnV005OJFt+efejw=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Date: Sat, 5 Sep 2015 14:52:29 +0300
From: Andrey Repin <anrdaemon@yandex.ru>
Reply-To: cygwin@cygwin.com
Message-ID: <1339527967.20150905145229@yandex.ru>
To: Dani Moncayo <dmoncayo@gmail.com>, cygwin@cygwin.com
Subject: Re: Problem with git and file mode changes
In-Reply-To: <CAH8Pv0j7y6-3d2Jwi1PzO1AXPVuXDc3S7tuAcVLEkGwEGJLE5w@mail.gmail.com>
References: <CAH8Pv0jXEEJ5P4jmojYne_SAt-DtK7twGLuujFCukoAhr1-f8g@mail.gmail.com>   <CAH8Pv0j7y6-3d2Jwi1PzO1AXPVuXDc3S7tuAcVLEkGwEGJLE5w@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit

Greetings, Dani Moncayo!

> Adam, Ken, thank you for taking time to help me.

> (BTW, did you keep my address in CC?  Because I didn't get any of your
> replies.  I had to check the mailing list web archive [1]).

Per the very purpose of mailing list, you're expected to subscribe for
conversation.
You can't really expect people to go to the trouble of checking if they need
to send additional copies or not.

> BTW(2): For the record, some data points I forgot to give in my initial post:
> * The underlying filesystem is NTFS.
> * I did not have this problem some weeks ago, with the same
>   system, Cygwin installation, and git repo.  Therefore, some
>   change/update in my system/environment must have introduced the problem.

> Ken's suggestion (setfacl -b test) didn't work, but it did work when I
> executed it on individual files (eg. 'test/rmailmm.el' instead of
> 'test').  So the problem is apparently fixed after doing:

>   find . -exec setfacl -b {} \;

> Thank you so much.

The idea of resetting ACL's on the top-level directory is to have a clean
start with the checkout. Doing it on an already existing tree may not yield
desirable results… as you've discovered yourself.

And if you ask me, a VCS that trying to preserve exact access mask is just
asking for trouble.


-- 
With best regards,
Andrey Repin
Saturday, September 5, 2015 14:40:23

Sorry for my terrible english...