Andy Levy wrote on Wed, Apr 27, 2011 at 20:05:54 -0400: > On Wed, Apr 27, 2011 at 19:43, Tech Geek <techgeek12...@gmail.com> wrote: > > We have a SVN server running on a Debian Linux box. Running svn > > --version returns: > > svn, version 1.6.12 (r955767) > > compiled Jul 28 2010, 08:58:12 > > > > Users uses TortoiseSVN client to access repositories residing on the > > SVN server. My question is it OK to use the latest TSVN client > > "TortoiseSVN-1.6.15.21042-win32-svn-1.6.16.msi" or should be stick to > > the older version of the TSVN client, > > TortoiseSVN-1.6.12.20536-win32-svn-1.6.15.msi, that we have been > > using? > > > > Although both the server and the client tools are 1.6.x based but i am > > not sure if the ".x" makes a big difference or not? > > All 1.x clients and servers are compatible via the RA layer. Some > features may be disabled when using versions that are too far > different (e.g. merge tracking won't work properly with a 1.3 server > and 1.6 client, but you can still commit your changes). > > If multiple clients are accessing a single working copy, they must all > be the same version (1.6.x, 1.5.x, etc.). If a newer client touches > the WC, the data format will be upgraded automatically and older > clients will no longer work.
For future reference, Subversion 1.7 clients will *not* auto-upgrade working copies. Only 1.5 and 1.6 clients do that, IIRC.
