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:message-id:in-reply-to:subject
	:mime-version:content-type:content-transfer-encoding; q=dns; s=
	default; b=x1yJZ65WhlgMTjjlru/bAyhfOmP4gD+F0KX7H8TsD1lczq3dxkM9E
	Kl7qkO2fCwytRHRBdFP5DpdEAv8UArNloDy1JPwA8XoNSUwL2vUX8V8crGgRA8Wd
	ffv9etFU2m+9fkM3Pmtskmnep3th4C7FDdkewmnmv68gbk0ZEy7hws=
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:message-id:in-reply-to:subject
	:mime-version:content-type:content-transfer-encoding; s=default;
	bh=a+9mV7YVfL2iQO7lWHWgbL7pRjU=; b=cxSILSOx0o4hVf/kL68lIIW0KOPs
	hd1hhgaxou2NOGNqOGmhlFL+Er93NjKvTGtmZlr2qtjl5aFQdiIgpd1rWjXE5LAD
	ieIc/rwsJREc1tZBQJHCwr+NfzzQsNMM2Mki/CXWs6MPubjKgEq1E/ThOviTrwPa
	YvUDwgfQoBbXqXQ=
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=0.9 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,RP_MATCHES_RCVD,SPF_PASS autolearn=ham version=3.3.2
X-HELO:	resqmta-po-10v.sys.comcast.net
Date:	Sun, 22 Nov 2015 23:30:27 +0000 (UTC)
From:	boulderfans AT comcast DOT net
To:	cygwin AT cygwin DOT com
Message-ID:	<1271139068.9180259.1448235027708.JavaMail.zimbra@comcast.net>
In-Reply-To:	<1032375163.9174650.1448234447549.JavaMail.zimbra@comcast.net>
Subject:	Git issue.
MIME-Version:	1.0
X-IsSubscribed:	yes

I've run into a problem when using the --git-dir option in git. It appears to have been introduced since git 2.4.x.

Here's an example of the problem using a locally built version (2.6.3) of git with some annotated error output:

[/cygdrive/d/projects]
$ git --version
git version 2.6.3-cyg

[/cygdrive/d/projects]
$ git --git-dir=d:/projects/git-git/.git config alias.foo ls-files
error: Unable to open tempfile: /cygdrive/d/projects/d:/projects/git-git/.git/config.lock
error: could not lock config file d:/projects/git-git/.git/config: No such file or directory

The problem is that the code that is checking the --git-dir option doesn't work properly if you use a DOS drive:/path specification. I tracked it down to the fact that has_dos_drive_prefix() is not implemented and always returns false.  From git-compat-util.h:

#ifndef has_dos_drive_prefix 
static inline int git_has_dos_drive_prefix(const char *path) 
{ 
return 0; 
} 
#define has_dos_drive_prefix git_has_dos_drive_prefix 
#endif 

It looks like there is an implementation of the function for a MinGW build (compat/mingw.c) but not for the Cygwin build. There were changes in this area about a year ago, but I'm not exactly sure what changed to cause this problem to appear.

Thanks. 

-Matt 

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

- Raw text -