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: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=
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:date:from:to:subject:message-id:references
	:mime-version:content-type:in-reply-to; s=default; bh=xriNjCjDbT
	g6YLnvhWHDjs/Yg18=; b=gbHVXb6KA4S1KsGTmpdqzETjAKCriIhTdBVlIomtci
	+i/WLU1lpi2fKFnc8lxdsTSUJa2Glos+MbtpijDwUJ287mjNYHDtvya8z5UGjj4c
	F5baqx2/BoCnZF2I1rUJIqFDxKVPQKqF478WkiV3HwIC1h39SJn2VmrzKZ0ELdC5
	A=
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=-2.6 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2 spammy=H*MI:sk:5717F1E, H*f:sk:5717F1E, H*i:sk:5717F1E, pain
X-HELO: mail-wm0-f54.google.com
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;        d=1e100.net; s=20130820;        h=x-gm-message-state:date:from:to:subject:message-id:references         :mime-version:content-disposition:in-reply-to:user-agent;        bh=q9BLbWBJu1MpSbwblWraj6B3bH4sylQjdgwALxu4nWM=;        b=AjZ/KpXf4+gzAXYZy3A2EiP7Izl90jfwXXwVXDfH07gdGCYfQVdROXqQLz4Ry4QaPE         MTdIFd2wZNYUsWCboT9ixKjYFoS8QCWb1JdN/oRHEyYNd9oNpvT1xMiWEoDxwG8RuzdY         7E4g7rdTktXLXNE5j0slTmHRa3/dYFcRgP6+BkVROAYGadEd4b5WWITTxx7JtKpAbJxj         oB3EiSpGE9bJ4J7OpwqggKX1FrA4FcZbS94zp8xnHituKqJt+Bk6C9Jbxh/UvTQxH65j         bk25O+4PUsvhsTMGQPGVQNrdoRFGKUWgwpC2YFHa5ocNpQUBbpAB4wtDTTNkv0ZazSzb         MU0g==
X-Gm-Message-State: AOPr4FUgOw3DpNVpH1yvzBuMGFV3m3SlJoR4egC8zrisQAwqowf7I0MlSOzb4oWFdXZAbg==
X-Received: by 10.195.11.197 with SMTP id ek5mr10774503wjd.58.1461190995470;        Wed, 20 Apr 2016 15:23:15 -0700 (PDT)
Date: Wed, 20 Apr 2016 23:23:13 +0100
From: Adam Dinwoodie <adam AT dinwoodie DOT org>
To: cygwin AT cygwin DOT com
Subject: Re: introduction, fix for npm w.r.t. git, and questions
Message-ID: <20160420222313.GM2345@dinwoodie.org>
References: <BLUPR03MB230DECD3A735AF3CB2225CBDF6D0 AT BLUPR03MB230 DOT namprd03 DOT prod DOT outlook DOT com> <20160420185011 DOT GJ2345 AT dinwoodie DOT org> <5717D8D9 DOT 2030600 AT gmail DOT com> <20160420205904 DOT GK2345 AT dinwoodie DOT org> <5717F1EF DOT 2030705 AT gmail DOT 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)
X-IsSubscribed: yes

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