DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:content-type:mime-version:subject:from
	:in-reply-to:date:content-transfer-encoding:message-id
	:references:to; q=dns; s=default; b=eCsDEKSwJl6PSknld0PXfzvzHEk8
	muMhP3gXl/0j1Uja2QFnjmS7sU4ROVMpniva77PGzPLjH4/VwFm/0aRb167eBoaV
	8ARfnsLg7uUl32go5G2KyDIECDQodoo1ax9nHK9kQb89qBIaPL3TJSORLeSkVV7N
	3cU165nj+zQ/yfg=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\))
Subject: Re: git fails to push
From: Warren Young <wyml@etr-usa.com>
In-Reply-To: <5502264B.3050803@lysator.liu.se>
Date: Mon, 16 Mar 2015 15:45:06 -0600
Message-Id: <C31449BA-B14C-4047-981B-6980AB755309@etr-usa.com>
References: <5502264B.3050803@lysator.liu.se>
To: The Cygwin Mailing List <cygwin@cygwin.com>
Content-Transfer-Encoding: 8bit

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

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


[*] http://git-scm.com/book/en/v2/Git-on-the-Server-The-Protocols
--
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