delorie.com/archives/browse.cgi | search |
X-Recipient: | archive-cygwin AT delorie DOT 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 23:02:09 +0400 |
From: | Andrey Repin <anrdaemon AT freemail DOT ru> |
Reply-To: | Andrey Repin <cygwin AT cygwin DOT com> |
Message-ID: | <38581395.20111117230209@mtu-net.ru> |
To: | Andy Koppe <andy DOT koppe AT gmail DOT com>, cygwin AT cygwin DOT com |
Subject: | Re: Rolling back to 1.6.x Subversion |
In-Reply-To: | <CAHWeT-ZtdYPK77RYXae6hG4WNKJtcO36CEsUUfUz2MRUp2B7uQ@mail.gmail.com> |
References: | <D0CBCC01C005D44CB4009B8A6B532BE41F0B731B AT IAD2MBX11 DOT mex02 DOT mlsrvr DOT com> <CAHWeT-ZtdYPK77RYXae6hG4WNKJtcO36CEsUUfUz2MRUp2B7uQ AT mail DOT gmail DOT com> |
MIME-Version: | 1.0 |
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 |
Greetings, Andy Koppe! > Can one use different svn clients on the same working copy, even if > they are the same version? You can even use them (literally) simultaneously. Subversion introduced an appropriate locking mechanics to ensure as much as possible that all transactions are atomic. But, as you pointed out, they all must be of the same version. > I've always been wary of that due to fear > of subtle differences in working copy format. Working copy format is dictated by the Subversion client layer http://svnbook.red-bean.com/en/1.7/svn.developer.layerlib.html#svn.developer.layerlib.client not by a program or moon phase. > Character encoding and line endings are two possible trouble spots that come > to mind. Subversion on inside using UTF-8. But this could be a problem when dealing with files outside Subversion. > 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. This could only happen, if you intentionally set svn:eol-style to "native". Otherwise, it will preserve line endings, or even convert them to the desired format upon submission. -- WBR, Andrey Repin (anrdaemon AT freemail DOT ru) 17.11.2011, <22:52> 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
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |