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
	=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Message-ID: <5508284B.1040304@lysator.liu.se>
Date: Tue, 17 Mar 2015 14:12:43 +0100
From: Peter Rosin <peda@lysator.liu.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@cygwin.com
Subject: Re: git fails to push
References: <5502264B.3050803@lysator.liu.se> <C31449BA-B14C-4047-981B-6980AB755309@etr-usa.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@lysator.liu.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