DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:mime-version:date:message-id:subject:from:to
	:content-type; q=dns; s=default; b=YALc26Mu1pWqngFeERfOlF5diVN8L
	7VXkPZ6Yjipn22eq6XY1gix4fsslUMbWwfnKEeeZfq8rBHj6FJxbCLpU1sqn+QAe
	pmuEKafcKBKVobKhf69+kSHoy3yMwP4qr7KE4BZaK5KO5oqG8BIALYsffkJ8ELWZ
	caDDMvZUSIjhC8=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
MIME-Version: 1.0
Date: Mon, 16 May 2016 09:03:38 -0400
Message-ID: <CADMefsbnkZ8tXE0A7ww+f0u5DPdLJVqHUPmLYVdu5i57fjQkBg@mail.gmail.com>
Subject: RE: Possible issue with newest version of git (v 2.8) under Cygwin
From: andrew stern <astern DOT fix8 DOT forum AT gmail DOT com>
To: cygwin AT cygwin DOT com
Content-Type: text/plain; charset=UTF-8

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

I would agree if it wasn't for the fact that even without looking at
the permissions tab we ended up with the inability for anyone else in
the group to write or update the head for the repository.  This is a
much bigger issue then just a display issue in Windows.  It is causing
read write permission issues where members can't push changes from
their local trees after another team member pushes their changes.  It
seems to mess it up in such a way that a system admin must reset
permissions after each push so that another team member can push their
changes.  This just started happening after updating cygwin in the
last few weeks and is related to changes to the ACL that were done in
the last couple of months.

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