DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:to:subject:message-id:references
	:mime-version:content-type:in-reply-to; q=dns; s=default; b=xQZ0
	M3O329iI/tbEG+rMYgTtESNPDar5dbG6lLgQFBnIrLQ8C7sVT1tZoX9Mn+2ZobYS
	S9NHFSQ/OEP+mBI7+T6hAp4dsMw34VJlvv/2yVRxoXF/Seqav77qPMJixCuUOT0f
	s0mi1AJtcjXqtdy9p04AoPKpG008k8A6WVS76P0=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Date: Wed, 20 Apr 2016 23:23:13 +0100
From: Adam Dinwoodie <adam@dinwoodie.org>
To: cygwin@cygwin.com
Subject: Re: introduction, fix for npm w.r.t. git, and questions
Message-ID: <20160420222313.GM2345@dinwoodie.org>
References: <BLUPR03MB230DECD3A735AF3CB2225CBDF6D0@BLUPR03MB230.namprd03.prod.outlook.com> <20160420185011.GJ2345@dinwoodie.org> <5717D8D9.2030600@gmail.com> <20160420205904.GK2345@dinwoodie.org> <5717F1EF.2030705@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <5717F1EF.2030705@gmail.com>
User-Agent: Mutt/1.5.21 (2010-09-15)

On Wed, Apr 20, 2016 at 11:17:35PM +0200, silverwind wrote:
> On 4/20/16 10:59 PM, Adam Dinwoodie wrote:
> >native Windows and Cygwin.  It's been a while since I tried it, but I
> >_think_ you can generally use Cygwin Git and Windows Git on the same
> >working copy without any difficulties, at least if you avoid the common
> >pain points like line ending rewriting and symlinks.
> 
> I've tried the native Windows version of git while debugging this,
> and yes, it accepts Windows-style paths correctly.
> 
> The deal-breaking issue with it for me was that it trashed the file
> permissions under Cygwin. Every file it touched (be it through
> clone, add or any other operation) was set to mode 777, so `git
> config core.fileMode false` would've been necessary to stay sane,
> but that of course comes with the drawback of not being able to
> change file modes.

Yes, that's definitely a catch; Windows seems to like to have executable
flags on more-or-less everything.

You can, if necessary, change filemodes with `git update-index
--chmod=+x <file>` (or `--chmod=-x` to remove the executable flag);
that'll stage the change to be committed when you run `git commit`,
without touching the permissions on the actual checked out files.
You're still not changing the file modes on the files you have checked
out, but you're at least making the change for anyone else who uses your
commits.

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