X-Recipient:	archive-cygwin AT delorie DOT 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:from:subject:to:references:message-id:date
	:mime-version:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=xzpVfyxumF7uj2T7
	ETJ6Lh4dwzV3dJMZh9txTyW3hw7JBsEW6SZqnXP/EzDnHFoAES1X3G9NPpCYGZzK
	2RVFEXg0kjrvwoGJvDdUgebE07N6tW3VZhHzgpVZg+J3STduzzZJbKQYKafLvWCt
	OP4AvkYjh7xxuDJuDQ2Q/3cruLM=
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:from:subject:to:references:message-id:date
	:mime-version:in-reply-to:content-type
	:content-transfer-encoding; s=default; bh=/tHXagxP3CV7cnobmXGJ9C
	wM9yw=; b=ruaZIsxXratD5PnW5X3QqpkI8RHVenoCmJ6ILiCrNdDFG1NhcEhH4c
	+nZ3YsDF9r0Dlrvypq+Owiwi6pt+6GdKYh0bFIkKIhROX0s3zSEPJ4ROsAGZTjBp
	GobKua1WyN42voroy0NTnbzWSWaX9ZUQwK9pci0gVdQC+eAaRFmeE=
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Authentication-Results:	sourceware.org; auth=none
X-Virus-Found:	No
X-Spam-SWARE-Status:	No, score=1.1 required=5.0 tests=AWL,BAYES_20,RP_MATCHES_RCVD,SPF_PASS autolearn=ham version=3.3.2 spammy=lies, ordering, dinwoodie, Dinwoodie
X-HELO:	endymion.arp.harvard.edu
From:	Norton Allen <allen AT huarp DOT harvard DOT edu>
Subject:	Re: Possible issue with newest version of git (v 2.8) under Cygwin
To:	cygwin AT cygwin DOT com
References:	<CADMefsagnTv23Jfi6St9VRpcabQJ9vekP2siT_Pfh=xO943QqQ AT mail DOT gmail DOT com> <20160514120353 DOT GH2345 AT dinwoodie DOT org>
Message-ID:	<57371B4A.1090708@huarp.harvard.edu>
Date:	Sat, 14 May 2016 08:34:18 -0400
User-Agent:	Mozilla/5.0 (Windows NT 10.0; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.7.2
MIME-Version:	1.0
In-Reply-To:	<20160514120353.GH2345@dinwoodie.org>
X-IsSubscribed:	yes

On 5/14/2016 8:03 AM, Adam Dinwoodie wrote:
>> If I leave off the noacl and do a clone followed by a push and pull we
>> >end up with the following error in the Windows security tab:
>> >   The permissions on file.cpp are incorrectly ordered, which may cause
>> >some entries to be ineffective.
> Yes, I've seen that before; it's a problem with the underlying
> cygwind1.dll rather than a problem with Git.  I believe the consensus
> from people on this list who know more about Windows permissions than me
> is that the warning is actually benign and can be ignored.

As I read the Cygwin documentation, the problem is that windows 
permissions and POSIX permissions don't line up very well. In order to 
faithfully reproduce POSIX permissions, Cygwin uses legal but 
non-standard ordering of ACEs. Windows' security tab thinks this is a 
problem, but it really isn't. To quote from the documentation here: 
https://cygwin.com/cygwin-ug-net/ntsec.html#ntsec-files:

    Unfortunately the security tab in the file properties dialog of the
    Windows Explorer insists to rearrange the order of the ACEs to
    canonical order before you can read them. Thank God, the sort order
    remains unchanged if one presses the Cancel button. But don't even
    *think* of pressing OK...

So it would seem the problem as such lies with Windows' security tab.

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

- Raw text -