From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 3500 invoked by alias); 17 Nov 2011 09:10:19 -0000 Received: (qmail 3492 invoked by uid 22791); 17 Nov 2011 09:10:18 -0000 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 Received: from mail-gx0-f171.google.com (HELO mail-gx0-f171.google.com) (209.85.161.171) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 17 Nov 2011 09:09:58 +0000 Received: by ggnk3 with SMTP id k3so145617ggn.2 for ; Thu, 17 Nov 2011 01:09:58 -0800 (PST) MIME-Version: 1.0 Received: by 10.50.169.99 with SMTP id ad3mr41174389igc.6.1321520997576; Thu, 17 Nov 2011 01:09:57 -0800 (PST) Received: by 10.68.47.5 with HTTP; Thu, 17 Nov 2011 01:09:57 -0800 (PST) In-Reply-To: References: Date: Thu, 17 Nov 2011 09:10:00 -0000 Message-ID: Subject: Re: Rolling back to 1.6.x Subversion From: Andy Koppe To: cygwin@cygwin.com Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-IsSubscribed: yes Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com X-SW-Source: 2011-11/txt/msg00295.txt.bz2 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). =C2=A0We 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