MIME-Version: 1.0
In-Reply-To: <D0CBCC01C005D44CB4009B8A6B532BE41F0B731B@IAD2MBX11.mex02.mlsrvr.com>
References: <D0CBCC01C005D44CB4009B8A6B532BE41F0B731B@IAD2MBX11.mex02.mlsrvr.com>
Date: Thu, 17 Nov 2011 09:09:57 +0000
Message-ID: <CAHWeT-ZtdYPK77RYXae6hG4WNKJtcO36CEsUUfUz2MRUp2B7uQ@mail.gmail.com>
Subject: Re: Rolling back to 1.6.x Subversion
From: Andy Koppe <andy.koppe@gmail.com>
To: cygwin@cygwin.com
Content-Type: text/plain; charset=UTF-8
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Precedence: bulk
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Content-Transfer-Encoding: 8bit

On 16 November 2011 23:06, Jim Garrison wrote:
>> -----Original Message-----
>> On Behalf Of Jeremy Bopp
>> Sent: Wednesday, November 16, 2011 9:18 AM
>> Subject: Re: Rolling back to 1.6.x Subversion
>>
>> That whole process is going to be unsupported here though, so is there
>> some reason you must remain on such an old release of subversion?
>
> Consider users who depend on clients (SVNKit) that don't
> yet have 1.7 native support (i.e. Subclipse).  We have to stay on
> 1.6 until ALL our clients support 1.7 due to the working copy
> restructuring.

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've certainly seen problems with CVS: Windows CVS clients often
convert to Windows line endings on checkout, whereas Cygwin CVS
doesn't, so if you check out with one and then do a 'cvs diff' with
the other, it says that every line has changed.

Andy

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