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=COsPz4E3aoiMIPezQRLrj0oPWsKUQgQbPeevp8/7J3Z
	L1/Mx36D4Sz4Heff1zM5lRPe0gc0rrtza3QKrCtDjvnu/DVYLqWzpPjCREFbVrxK
	0j9bTtkcZWyNWvnyskpf8rrTumdS8VosISIHCmnK4R4Us3EwquQ7lQH0byHk8cmE
	=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Message-ID: <5249A7CA.5050205@etr-usa.com>
Date: Mon, 30 Sep 2013 10:33:14 -0600
From: Warren Young <warren@etr-usa.com>
User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: Cygwin-L <cygwin@cygwin.com>
Subject: Re: What is wrong with SVN?
References: <52488201.8030104@alice.it>
In-Reply-To: <52488201.8030104@alice.it>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

On 9/29/2013 13:39, Angelo Graziosi wrote:
> What is wrong with this command:
>
> $ svn co svn://gcc.gnu.org/svn/gcc/branches/fortran-dev fortran-dev

What happens if you modify it a bit:

     $ CYGWIN_SQLITE_LOCKING=posix svn co svn://...

That forces the SQLite library that Cygwin's svn is linked to to use 
POSIX compatible locking, instead of the Windows compatible locking it 
uses by default.

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