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=TLEwObIG/kAktXc6
	2/Ze4Qt1rAmwJEc4MBBUZT4+4lAfxMjLRNTUwWGl9JZA7dOk/MPNE+CgCmlS6OqT
	QpDEZgbg/4mdlU5AH0fnyN8MlpdjwvM2c0P860XIyChTuxIiaSesvaYLKym8Wnrg
	bjigOvMNnvnN+/KgmDrSdVL7e1E=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Message-ID: <BLU182-DS23E73EC671521B950E6875D4420@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>
In-Reply-To: <56042985.2040104@tlinx.org>
Subject: Re: Issues encountered with new Cygwin version
Date: Fri, 25 Sep 2015 11:01:20 -0400
MIME-Version: 1.0
Content-Type: text/plain;	format=flowed;	charset="utf-8";	reply-type=original
Content-Transfer-Encoding: 7bit

On 24/09/2015 07:35, Marco Atzeri wrote:

> > 2) The 'touch' command creates a file with the executable bit set
> >
> > [user@hostname ~]$ touch newfile.txt
> > [user@hostname ~]$ ls -l newfile.txt
> > -rwxrwx---+ 1 user Domain Users 0 Sep 22 17:21 newfile.txt
>
> It likely depends on the inherited permissions from the directory

BINGO! Looks like starting 1.7.34 the file permissions were "fixed" to
exhibit this new behavior
(https://www.cygwin.com/ml/cygwin-announce/2015-02/msg00009.html). After
reverting back to 1.7.33 I was able to get the previous behavior back.

This is very unfortunate because I'm using Git in Cygwin specifically 
because it doesn't set the executable bit like Windows applications. With 
this new behavior, trying to rebase or cherry-pick causes merge conflicts 
because any file touched by Git will have the executable bit set. 
Additionally, trying to do a 'reset --hard' doesn't work anymore since the 
executable bit stays on with the new file permission behavior, so you'll 
never really return to the previous state.

Yes, I can always set 'filemode=false' to ignore file permissions, but I
still want to be able to enforce the correct file mode upon commits.
Suggestions?

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