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:subject:to:references:from:message-id:date
	:mime-version:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=QbJrWZQPXMKHT+ul
	oxiTL/Q0CQjVjAbkYB+jzX4crJVamu3ZITjZ8E9V3sfqm3TS4CVYlKAX7pzg6xcc
	rQQMmXVzk3HuLsLExON56h1jQSf6DuRXKM4nImiccGqXWE+3uSwpmvI7KfEjsL8D
	ukD5d+xZuQHfRJeXZmII6ZW6mG4=
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:subject:to:references:from:message-id:date
	:mime-version:in-reply-to:content-type
	:content-transfer-encoding; s=default; bh=geURxde+CETFNf7tT7gRhR
	tTBH8=; b=C/9igHERv0qYz9JDz7ZxFxM9ZHQ6s5PhdgXVk3aGaLBp0zsBy4DThb
	raJNHZm67Wg25gWCq1U+vGXICYiJi0AOpNft7bNGh8sJy4o8vZmBorGyJY5Lstt7
	uSh0jw346kfFUfBGvHu080nqlu2Bl8r1TvLGeZPkIsonEo4wxMjlk=
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=-1.2 required=5.0 tests=AWL,BAYES_00,RP_MATCHES_RCVD,SPF_PASS autolearn=ham version=3.3.2
X-HELO:	mail.lysator.liu.se
Subject:	Re: [cygwin] Re: git fails to push
To:	cygwin AT cygwin DOT com, adam AT dinwoodie DOT org
References:	<5502264B DOT 3050803 AT lysator DOT liu DOT se> <C31449BA-B14C-4047-981B-6980AB755309 AT etr-usa DOT com> <5508284B DOT 1040304 AT lysator DOT liu DOT se> <E043FEB21B394020B5EA3AFC2ED69308 AT black> <55083FC1 DOT 4010503 AT lysator DOT liu DOT se> <20150317171011 DOT GG20741 AT dinwoodie DOT org>
From:	Peter Rosin <peda AT lysator DOT liu DOT se>
Message-ID:	<55C3C797.3010109@lysator.liu.se>
Date:	Thu, 6 Aug 2015 22:46:15 +0200
User-Agent:	Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.1.0
MIME-Version:	1.0
In-Reply-To:	<20150317171011.GG20741@dinwoodie.org>

On 2015-03-17 18:10, Adam Dinwoodie wrote:
> On Tue, Mar 17, 2015 at 03:52:49PM +0100, Peter Rosin wrote:
>> Interesting. But the patch may not be needed. The easy thing to
>> do seems to be to either use core.createobject = rename
>> or to convince some git :-) that Cygwin also needs
>> 	OBJECT_CREATION_USES_RENAMES = UnfortunatelyNeedTo
>> in its section in config.mak.uname.
> 
> With my Git maintainer hat on, I'm not going to include that change in
> the Cygwin distributed version of Git unless and until I hear reports of
> `git config core.createObject rename` helping more people.
> 
> This is clearly not a common problem (it's the first I've heard of this
> sort of problem, and I've been using Git on Cygwin on NTFS for years
> without hitting these issues), so I'm very reluctant to inflict the
> disadvantages of using the "rename" object creation on everyone unless
> it's going to fix problems for enough people to make those disadvantages
> worthwhile.
> 
> (As it is, we haven't had verification that this change does anything
> anyway, but if it doesn't, the entire point is irrelevant...)

Sorry to reply this late to this old thing...

...but anyway, here are some further evidence of problems caused
by not always going with rename.

http://stackoverflow.com/questions/6866913/git-commit-on-windows-cygwin-is-broken

It seems like some people are migrating to msysgit over this issue.

Cheers,
Peter


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