delorie.com/archives/browse.cgi | search |
X-Recipient: | archive-cygwin AT delorie DOT com |
X-SWARE-Spam-Status: | No, hits=-2.5 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,TW_SV |
X-Spam-Check-By: | sourceware.org |
MIME-Version: | 1.0 |
In-Reply-To: | <D0CBCC01C005D44CB4009B8A6B532BE41F0B731B@IAD2MBX11.mex02.mlsrvr.com> |
References: | <D0CBCC01C005D44CB4009B8A6B532BE41F0B731B AT IAD2MBX11 DOT mex02 DOT mlsrvr DOT 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 DOT koppe AT gmail DOT com> |
To: | cygwin AT cygwin DOT com |
X-IsSubscribed: | yes |
Mailing-List: | contact cygwin-help AT cygwin DOT com; run by ezmlm |
List-Id: | <cygwin.cygwin.com> |
List-Unsubscribe: | <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT 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 |
X-MIME-Autoconverted: | from quoted-printable to 8bit by delorie.com id pAH9AM2I019827 |
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
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |