X-Recipient: archive-cygwin@delorie.com X-SWARE-Spam-Status: No, hits=-1.5 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Message-ID: <4EFB8FC1.7060307@bopp.net> Date: Wed, 28 Dec 2011 15:53:05 -0600 From: Jeremy Bopp User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:8.0) Gecko/20111124 Thunderbird/8.0 MIME-Version: 1.0 To: cygwin@cygwin.com Subject: Re: Distributed Git not compiled under Cygwin? References: <33047124.post@talk.nabble.com> In-Reply-To: <33047124.post@talk.nabble.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com On 12/28/2011 03:14 PM, cxira wrote: > > I noticed when using the Git that is distributed under the Cygwin setup (Git > v1.7.5.1-1) that, when creating a new repository, the core.filemode local > setting is set to true. Being under Windows, this should be false because of > how file permissions are handled. While lacking detail, the announcement about that version of Git mentions that there are some changes included to work around choices made upstream regarding file permissions management under Cygwin: http://cygwin.com/ml/cygwin/2011-05/msg00205.html This is nothing new for Cygwin's Git. There's a good chance that if you build from the Git sources distributed via setup.exe rather than the upstream sources, you will get a Git that behaves the same as the one shipped by setup.exe. All that said, I've never run into file permission issues using Cygwin's Git. You probably won't either as long as you don't need to host your repositories on FAT or FAT32 filesystems. If you would still prefer to have that setting set as per upstream while avoiding local builds, I believe you can set it as you need in /etc/gitconfig, and all repositories should inherit that setting unless the user explicitly overrides it in global or local config settings. I also remember reading somewhere once that you should be able create a configuration template that would be used by new repositories created by git init or git clone that can set the property as you need. I can't find any links for that at the moment though. :-/ -Jeremy -- 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