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:reply-to:message-id:to:subject
	:in-reply-to:references:mime-version:content-type
	:content-transfer-encoding; q=dns; s=default; b=auXJycUxvWEm33Sq
	sUHZXQBOyA9SwSn+wtpVHiPM9dM0NJRgL4SZuQR7FAICqKLvtN2nVBwO32KygMK1
	Y0ZDrDor3XocacUZeiVWW8XNjGBcHuXmEjU9E3McZDVCH60OzuQGNYTSC624UPO0
	YOrNYN3ri3SHZE+1vlzUC70x8qc=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Date: Tue, 27 Nov 2018 17:35:18 +0300
From: Andrey Repin <anrdaemon@yandex.ru>
Reply-To: cygwin@cygwin.com
Message-ID: <345670383.20181127173518@yandex.ru>
To: Adam Dinwoodie <adam@dinwoodie.org>, cygwin@cygwin.com
Subject: Re: Cygwin Git with Windows paths
In-Reply-To: <CA+kUOamKzp=jjKc1OLGo1vmepoee5ABwgUpYJF9Lq1CJjOBy9Q@mail.gmail.com>
References: <5bf10195.1c69fb81.27494.eed4@mx.google.com>   <CA+kUOamKzp=jjKc1OLGo1vmepoee5ABwgUpYJF9Lq1CJjOBy9Q@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Greetings, Adam Dinwoodie!

> Personally, I don't see this as a bug; AIUI using Windows style paths
> isn't something that is supported in general in Cygwin, even if it's
> something that works in some circumstances. I acknowledge that this
> causes problems for non-Cygwin tools using Cygwin Git, but the
> solution there is to either use Cygwin aware/native versions of those
> tools, or to use non-Cygwin versions of Git.

The problem with Git is that it relies on entire POSIX ecosystem, contrary to,
say, Subversion, which is just one drop-in binary.

> In particular, I'm wary of fixing this set of interop problem
> introducing some other problem; I'd prefer Cygwin tools to fail to
> handle Windows paths entirely than the current situation where "c:"
> refers to a file of that exact name in the current directory, and
> "c:\" sometimes refers to a completely different directory, when on
> *nix systems in general both would refer to files in the current
> directory.

Then it would just make Cygwin as useless as WSL.

> I see you've raised this on the Git mailing list as well, and if the
> upstream Git package starts to handle such paths, I'll take the
> relevant patches. However since I don't consider this a bug, I'm not
> going to raise it myself.


-- 
With best regards,
Andrey Repin
Tuesday, November 27, 2018 17:33:24

Sorry for my terrible english...


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