DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:reply-to:subject:references:to:from:message-id
	:date:mime-version:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=sEwYjC4lt3KsPaSZ
	LmUQ0coIYUA8EdcXb/V5zSJT3+7biZmMrllAW/E/0EGZqdxPtMORx4gIs8Zre2+s
	TJB7UirfOL+Ylqb5b7D/Q0HlccBR7B2aBd51doul/v1YY+Gf6t91Fpm8+s3WedgT
	02ifZVNpZsu7DjsVIm4enVJtJYs=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Reply-To: moss@cs.umass.edu
Subject: Re: Problem with git on cygwin64 on Windows 10 (2.8.3-1), again
References: <576EE695.10509@junovagen.se> <5771494C.1010401@junovagen.se> <578A5088.200@junovagen.se>
To: cygwin@cygwin.com
From: Eliot Moss <moss@cs.umass.edu>
Message-ID: <a2d9ec84-a281-f48d-3a33-0a8466fb468a@cs.umass.edu>
Date: Sat, 16 Jul 2016 12:57:20 -0400
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0
MIME-Version: 1.0
In-Reply-To: <578A5088.200@junovagen.se>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit

I know it may be grasping at straws, but I would look into the
permissions on the files.  Also, I can imagine that running
a more native Windows version of git, and the cygwin version
of git, over the *same checkout* might lead to problems around
permissions and such.

Regards -- Eliot Moss

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