X-Recipient: archive-cygwin@delorie.com X-SWARE-Spam-Status: No, hits=3.5 required=5.0 tests=AWL,BAYES_50,FREEMAIL_FROM,KAM_THEBAT,TW_SV X-Spam-Check-By: sourceware.org Date: Thu, 17 Nov 2011 11:39:45 +0400 From: Andrey Repin Reply-To: Andrey Repin Message-ID: <1872837516.20111117113945@mtu-net.ru> To: Jeremy Bopp , cygwin@cygwin.com Subject: Re: Rolling back to 1.6.x Subversion In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: 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 Greetings, Jeremy Bopp! > 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. On my memory, it wasn't changed even once in four years. Or all changes were transparent. The main problem with 1.7 I see myself, I described earlier: No way to tell at a glance, if the directory you're working with is versioned or not. -- WBR, Andrey Repin (anrdaemon@freemail.ru) 17.11.2011, <11:06> Sorry for my terrible english... -- 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