X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-1.4 required=5.0	tests=AWL,BAYES_00,TW_SV
X-Spam-Check-By: sourceware.org
Message-ID: <4EC53744.9050205@bopp.net>
Date: Thu, 17 Nov 2011 10:33:08 -0600
From: Jeremy Bopp <jeremy AT bopp DOT net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: Rolling back to 1.6.x Subversion
References: <D0CBCC01C005D44CB4009B8A6B532BE41F0B731B AT IAD2MBX11 DOT mex02 DOT mlsrvr DOT com>	<CAHWeT-ZtdYPK77RYXae6hG4WNKJtcO36CEsUUfUz2MRUp2B7uQ AT mail DOT gmail DOT com> <CAEhDDbDJ6_BvfjgFGaUWSduMSLdVJRYNUP6TCutRKCO=4FfuHA AT mail DOT gmail DOT com>
In-Reply-To: <CAEhDDbDJ6_BvfjgFGaUWSduMSLdVJRYNUP6TCutRKCO=4FfuHA@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes
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

On 11/17/2011 05:12, Csaba Raduly wrote:
> On 11/17/11, Andy Koppe  wrote:
>> Can one use different svn clients on the same working copy, even if
>> they are the same version? I've always been wary of that due to fear
>> of subtle differences in working copy format. Character encoding and
>> line endings are two possible trouble spots that come to mind.
> 
> I regularly use Cygwin's SVN and Subclipse in a Windows version of
> Eclipse and never had any problems. I had to postpone upgrading to the
> Subversion 1.7 Cygwin package until Subclipse 1.8 came out, which
> supports the 1.7 working copy format.

One of the really smart things that the SVN project has done is insulate
the working copy from most of the horrors of line ending differences.
The administrative files appear to either have a strict line ending
definition for all platforms or (more likely) clients are expected to be
flexible regarding line ending handling within the files.  The use of
the svn:eol-style property on source files allows for a great deal of
flexibility regarding management of line endings within the working copy.

Ultimately, any problems boil down to the text editors in use and not
the various SVN clients.  As far as I can see, only the combination of
setting svn:eol-style to native and using a crummy text editor could
expose unexpected problems when mixing Cygwin and Windows SVN clients
within a single working copy.  Those problems would really only be in
the text editor and not SVN however since the text editor could receive
a file with unsupported line endings if the Cygwin client checked the
file out.  Either SVN client would do the right thing with the file upon
commit regardless of the line endings it ended up having after editing.

There can't be very many users out there mixing both Cygwin and Windows
SVN clients with a text editor that completely chokes on Unix line
endings. :-)  I've been really impressed with how gracefully SVN handles
this whole line ending issue.

-Jeremy

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