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:message-id:date:from:mime-version:to:subject
	:references:in-reply-to:content-type:content-transfer-encoding;
	 q=dns; s=default; b=WH3f1FKvjH8DuRu12Hb9JqeB3Xaw/fE/SnVZfMePDKS
	ZwGd0LUXYtJP3RQMg8ld9FijQBQ6GWUVt8xpQRePrFi3Tzjck+oFoXY2DSwWQeZu
	Lwdn9ZIJn+QP4PHaCPZ17n2iT1GdmAOIoeYpkKkuKwABPH+9412GzZZ2n9ad46zg
	=
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:message-id:date:from:mime-version:to:subject
	:references:in-reply-to:content-type:content-transfer-encoding;
	 s=default; bh=b6EADExaCi2mnkD4fKNr/d4pyrk=; b=wBY2D5G18CiQI6xUv
	9UK7Lsq1a+7WgASJKIO54FrtUhhjyTU361nSavks6t8xQdPOuFsB0NTKD4VX8cQ9
	F/RKhDa55j529rEuNQusNZO2RyQPkitiYwZk9RA8ruwqyu629Hou9ZrtcBalzpdR
	fygd9g+vq+9AdEyi4glaIy/0Pc=
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.5 required=5.0 tests=AWL,BAYES_00,SPF_PASS,T_RP_MATCHES_RCVD autolearn=ham version=3.3.2
X-HELO: mail.lysator.liu.se
Message-ID: <5508284B.1040304@lysator.liu.se>
Date: Tue, 17 Mar 2015 14:12:43 +0100
From: Peter Rosin <peda AT lysator DOT liu DOT se>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: git fails to push
References: <5502264B DOT 3050803 AT lysator DOT liu DOT se> <C31449BA-B14C-4047-981B-6980AB755309 AT etr-usa DOT com>
In-Reply-To: <C31449BA-B14C-4047-981B-6980AB755309@etr-usa.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit

On 2015-03-16 22:45, Warren Young wrote:
> On Mar 12, 2015, at 5:50 PM, Peter Rosin <peda AT lysator DOT liu DOT se> wrote:
>>
>> To file:///cygdrive/x/some path/with spaces/repo.git
> 
> You shouldn’t be doing anything shared-database-like to a network drive.  Network file sharing protocols typically either A) do not do locking correctly, or B) they run slow as molasses in order to provide proper locking semantics.  Since almost no one is willing to accept option B), you usually get option A).

Even if you claim that I shouldn't do something and then list a couple
of reasons for that, you have no way of knowing if these reasons apply
or if the alternative is even worse.

I am the only person who has ever pushed to the repo in question.
Speed is not an issue, I push fairly seldom. The code base is stable.

> I think if you set Git up on the server using one of the supported server protocols [*] your problem will go away.

You almost make it sound like file:// isn't a supported server protocol.
Isn't it? If not, why is it listed under "Git on the Server" and why
is NFS mounts mentioned?

I realize that you are trying to help me work around the problem, but
finding a workaround isn't my motivation for posting here (I have a big
enough toolbox to find plenty myself). In fact, I don't think the real
problem is in the git code base. It feels more like some generic file
access race that manifests itself as freshly created files not being
found, or something like that.

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