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:mime-version
	:content-type:in-reply-to; q=dns; s=default; b=BYZkjIi31R8p+XM0M
	5zF6IphXreVp8c6lozQ3WZFdp7628X0XKR+IiyIbWyemNPwEscOYOYa1XAbqb93a
	cxP6bx5R7/5QRqA50t6tKH38aAS4qjrwE+44UbSnMS1dvrhg6nyHeqyuSkX9ekb2
	ZVfhMZfhKESJ59MbNKEg/6AAMI=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Date: Wed, 20 Apr 2016 17:45:48 +0100
From: Adam Dinwoodie <adam AT dinwoodie DOT org>
To: cygwin AT cygwin DOT com
Subject: Re: git and absolute Windows-style paths
Message-ID: <20160420164548.GI2345@dinwoodie.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <5717A3EF.6030407@gmail.com> <5717ACA1.2060003@gmail.com>
User-Agent: Mutt/1.5.21 (2010-09-15)

On Wed, Apr 20, 2016 at 05:44:47PM +0200, silverwind wrote:
> > I can't immediately see what's going wrong, so I'm going to report
> this upstream.
> 
> Thanks. I came upon this issue through npm which is using these
> Windows paths for certain git operations. Unfortunately, The npm
> team is very reluctant when it comes to merging Cygwin-specific
> patches, so chances of landing a fix on their side are rather slim.
> 
> Is there a public repository for the git package used by Cygwin?

The main Git repository[0] includes a bunch of Cygwin specific code
already, and I maintain a repository of the packaging paraphernalia[1]
which includes a couple of patches that aren't yet in the upstream code.

[0]: https://git.kernel.org/cgit/git/git.git/
[1]: http://github.com/me-and/Cygwin-Git

On Wed, Apr 20, 2016 at 06:21:53PM +0200, silverwind wrote:
> I think a floating patch to Cygwin's git 
> package would be more appropriate, unless it can be addressed in 
> Cygwin's system calls (which I'm sure has been attempted).

As the Git maintainer for Cygwin, I'm not willing to maintain a
downstream patch to make Cygwin Git handle Windows-style paths, and I
don't think there's much chance of one being accepted into the upstream
Git source code (although you're obviously welcome to try getting such a
patch accepted).

If you need to be able to pass Windows-style paths to Cygwin
applications, you should write a wrapper function or script that calls
`cygpath` to do the conversion.  Anything else is liable to work
intermittently at best; Cygwin applications in general expect
POSIX-style paths, given the aim of the Cygwin project is to provide a
POSIX-like environment.

Adam

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