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:subject:to:references:from:message-id:date :mime-version:in-reply-to:content-type :content-transfer-encoding; q=dns; s=default; b=VEI1mDzHw9rFzjn0 m98CuPsmAuIhNULi0014cnpAGQFS0ziQO3LNp7pipqGh/h4vnLwxiilI44xT6IBu H779S0KN3dTe23eoxIijLYvPxYT+7z0GcVVZi4Xkbjn2vWQy7hRtrDr7lLBOdDHp AquYojcPPrVV/J56pCFIu48K4WM= 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:subject:to:references:from:message-id:date :mime-version:in-reply-to:content-type :content-transfer-encoding; s=default; bh=Z6xHZqowUA36g7YRDt6D4Q jQuuc=; b=DB0fEI5HDmWDeHJxRqZyqG3U8hRIlB7jp6LaoXTmvsrbAETW94E7Cn h9QR2sdWLoJnlglE1pgR0xACRUczdJDXdL8MTLi8dYMqHFCYPudSLRpzGhG8dd6R fnMXIwB1pF1WgRTqqhcvYuYA7g56Nz65r6uQqOwrkxye+m4SVTfTk= Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , 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.9 required=5.0 tests=AWL,BAYES_00,RP_MATCHES_RCVD,SPF_HELO_PASS,SPF_PASS autolearn=ham version=3.3.2 X-HELO: limerock02.mail.cornell.edu X-CornellRouted: This message has been Routed already. Subject: Re: Issues encountered with new Cygwin version To: cygwin AT cygwin DOT com References: <154887677 DOT 20150923111537 AT yandex DOT ru> <56036256 DOT 8080209 AT tlinx DOT org> <56037F66 DOT 40209 AT tlinx DOT org> <56042985 DOT 2040104 AT tlinx DOT org> From: Ken Brown Message-ID: <560566EA.3010503@cornell.edu> Date: Fri, 25 Sep 2015 11:23:22 -0400 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.2.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes On 9/25/2015 11:01 AM, Walter L. wrote: > 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? I think you misunderstood what Marco was saying. If the problem is caused by the default ACL on the directory, you could fix that ACL. Ken -- 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