X-Recipient: archive-cygwin AT delorie DOT com
X-Spam-Check-By: sourceware.org
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; 	charset="iso-8859-1"
Subject: RE: Subversion problems with "svn switch", "svn co", "svn switch", because of 'wrong' permissions in .svn/ directories
Date: Tue, 29 Apr 2008 12:58:53 +0200
Message-ID: <F0D7281DAB048B438E8F5EC4ECEFBDDC02CFD503@esmail.elsag.de>
References: <20080419165955 DOT GD11912 AT trikaliotis DOT net> <20080421102419 DOT GA18922 AT trikaliotis DOT net> <045401c8a39b$78a3d3c0$2708a8c0 AT CAM DOT ARTIMI DOT COM> <20080423170816 DOT GA463 AT mersenne DOT largestprime DOT net> <20080426094145 DOT GB9172 AT trikaliotis DOT net> <041701c8a984$cbec3010$2708a8c0 AT CAM DOT ARTIMI DOT COM> <F0D7281DAB048B438E8F5EC4ECEFBDDC02CFD48E AT esmail DOT elsag DOT de> <045001c8a9da$079ea020$2708a8c0 AT CAM DOT ARTIMI DOT COM>
From: =?iso-8859-1?Q?J=F6rg_Schaible?= <Joerg DOT Schaible AT Elsag-Solutions DOT com>
To: <cygwin AT cygwin DOT com>
X-IsSubscribed: yes
Reply-To: cygwin AT cygwin DOT com
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
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id m3TAxG9X032405

Dave Korn wrote:
> Jörg Schaible wrote on 29 April 2008 07:39:
> 
>> cygwin-owner AT cygwinWOOPS wrote:
> 
>   Say, has your Outlook Quotefix gone screwy too?
> 
>>> Spiro Trikaliotis wrote on 26 April 2008 10:42:
>>> 
>>>> Unfortunately, with SVN from Cygwin, this is not true anymore. For
>>>> the Cygwin version of SVN, the "native" format for text files uses
>>>> Unix line endings (LF) only. 
>>>> 
>>>> As there a way to get it fixed? Or is it again something for
>>>> upstream?
>>> 
>>>   A config item to override the default setting for "native"
>>> eol-style might well be a useful feature enhancement patch for
>>> upstream; it would be useful on all platforms, not just Cygwin.
>> 
>> Well, Cygwin's Subversion simply does not respect text mounts
>> (compared to CVS) and that's hardly something for upstream.
>> 
> 
>   Hmm, well it might or might not be, it depends what method it's
> using to determine the native mode.
> 
>   If it was simply fopen()ing a file in text mode and writing, it
> would of course "respect" textmode mounts automatically.  Perhaps it
> manages it all manually by always writing in binary mode, and it
> inherently assumes that all filing systems operate in the same
> textmode, and some test it does misleads it?
> 
>   It also depends on the attitude of the upstream maintainers to
> accepting platform-specific patches.

Well, it might be very well that Subversion always uses binary mode for file I/O, it will even convert text files on its own if the svn:eol-style property is set (unless your file has no mixed EOLs). OTOH it cannot know that an environment uses two different native modes, that's quite a Cygwin speciality. So, it's some kind of catch-22 ;-)

- Jörg

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/