DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:subject:to:references:from:message-id:date
	:mime-version:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=eeJqxmfPt9O1mtdF
	zDsay7Sq0JiV+kLWoWUALPbSvzDPEsIp08Y7xnQoUqodr2vz9T9oPNldPYUTY4d5
	ruJ/VR6LKz070CmqfdIBGKWUYqjPdpvhabRJyTEH+HTVlAj37U8F9LvJFPQSMwye
	e5nGTygctgjz7XH1tcCbuTaAQjA=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Subject: Re: git and absolute Windows-style paths
To: cygwin@cygwin.com
References: <57169662.9060503@gmail.com> <e8b47924c6ff4f07993627dbb26f7066@ntmaexbe04.bedford.progress.com> <5717A3EF.6030407@gmail.com> <5717A5C6.5060001@cs.umass.edu>
From: silverwind <silv3rwind@gmail.com>
Message-ID: <5717ACA1.2060003@gmail.com>
Date: Wed, 20 Apr 2016 18:21:53 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.5.0
MIME-Version: 1.0
In-Reply-To: <5717A5C6.5060001@cs.umass.edu>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit

Hey,

> I think that tackling this with a script/function is a better approach ...

That's seems like a bandaid solution from which the general user base 
would not be able to profit. 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).

Why can I

   cat c:\\file.txt

but can't

   git add c:\\file.txt

? Where is this path normalization magic happening?

Regards,
Roman

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