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: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=
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:message-id:from:to:references:in-reply-to
	:subject:date:mime-version:content-type
	:content-transfer-encoding; s=default; bh=aXf28Pf8+eKny+juY+OMWm
	r4Hj8=; b=m2ORF9Lo4tbFfvR+ibMsleHAfX2Lc5T8YLDpTDp+UbaEvAeO9F+GnG
	AzJUVLCi98CA4ufuyIhh4fVo/eqjgnjPmZAOCq0SJnyhlUg57BNvzAmMY5bwNrpC
	ShlychfTFkcFh5EoAx8fHWoNVwAVT+i/p1gMuqiFW4sihDlZFVORg=
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=0.1 required=5.0 tests=BAYES_50,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,RP_MATCHES_RCVD,SPF_PASS autolearn=ham version=3.3.2
X-HELO:	BLU004-OMC1S1.hotmail.com
X-TMN:	[VZeHS1a0Da1Cmxey1lXNUqwu8Xy1snZI]
Message-ID:	<BLU182-DS23E73EC671521B950E6875D4420@phx.gbl>
From:	"Walter L." <bournenoir AT hotmail DOT com>
To:	<cygwin AT cygwin DOT com>
References:	<BLU182-W10FB6B21A2AEC90F71470FD4450 AT phx DOT gbl> <154887677 DOT 20150923111537 AT yandex DOT ru> <BLU182-DS2B4F831FEB7E4C1B67330D4440 AT phx DOT gbl> <56036256 DOT 8080209 AT tlinx DOT org> <BLU182-DS2567923242507AF88D9315D4430 AT phx DOT gbl> <56037F66 DOT 40209 AT tlinx DOT org> <BLU182-DS177F609D3B4BC69A880C77D4430 AT phx DOT gbl> <56042985 DOT 2040104 AT tlinx DOT 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

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

> > 2) The 'touch' command creates a file with the executable bit set
> >
> > [user AT hostname ~]$ touch newfile.txt
> > [user AT 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

- Raw text -