X-Recipient: archive-cygwin@delorie.com X-SWARE-Spam-Status: No, hits=0.1 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_LOW X-Spam-Check-By: sourceware.org From: Jim Garrison To: "cygwin@cygwin.com" Date: Wed, 16 Nov 2011 18:06:11 -0500 Subject: RE: Rolling back to 1.6.x Subversion Message-ID: Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 X-IsSubscribed: yes Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id pAGN6cB9014265 > -----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? Um... 1.7 just came out in the last few months, 1.6.17 isn't "such an old release". 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. When 1.7 came out I saved a copy of the 1.6.17 distribution locally. -- 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