From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13145 invoked by alias); 17 Nov 2011 00:53:48 -0000 Received: (qmail 13131 invoked by uid 22791); 17 Nov 2011 00:53:47 -0000 X-SWARE-Spam-Status: No, hits=0.1 required=5.0 tests=BAYES_20,TW_SV X-Spam-Check-By: sourceware.org Received: from mail32.mailforbusiness.com (HELO mail32.mailforbusiness.com) (64.106.245.205) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 17 Nov 2011 00:53:32 +0000 Received: from mail32.mailforbusiness.com (localhost [127.0.0.1]) by mail32.mailforbusiness.com (Postfix) with ESMTP id 086B75DAE8 for ; Wed, 16 Nov 2011 19:53:31 -0500 (EST) Received: from [192.168.2.18] (rrcs-71-42-237-82.sw.biz.rr.com [71.42.237.82]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) (Authenticated sender: jeremy@bopp.net) by mail32.mailforbusiness.com (Postfix) with ESMTPSA id A53265DAE6 for ; Wed, 16 Nov 2011 19:53:30 -0500 (EST) References: User-Agent: K-9 Mail for Android In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Subject: RE: Rolling back to 1.6.x Subversion From: Jeremy Bopp Date: Thu, 17 Nov 2011 00:53:00 -0000 To: "cygwin@cygwin.com" Message-ID: 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/msg00289.txt.bz2 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? > >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. Seems that I stepped on some nerves due to my poor choice of wording. Sorry about that. All I really wanted to know was why it was important to hang back from the latest available version when getting the older one was less than trivial. Not using anything more than the command line for svn (infrequently at that) made me forget how often that project changes formats in the working copies and the ramifications of that behavior. Thanks for enlightening me. :-) -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