Hi Stefan
On Thu, Jul 3, 2014 at 4:47 PM, Stefan Sperling <s...@elego.de> wrote: > On Thu, Jul 03, 2014 at 10:58:35AM +0100, Notes Jonny wrote: >> I guess the other idea is to promise to only allow ".svn format" >> updates every 5 years? I can't think that I've noticed any >> improvements since I've been using new formats.. > > The 1.8 format added support for local move tracking, for instance. > http://subversion.apache.org/docs/release-notes/1.8.html#moves Many thanks for your reply. I'm still suffering the version collisions. I was going to join tortoise svn users list, but I thought as I am already discussing here I will ask you. I've installed TortoiseSVN 1.7.7 (which uses svn 1.7.5) and it can't access the checkout from Jenkins (which is supposed to be "1.7" format). Actually Tortoise is offering to upgrade to "1.7". I am a bit surprised as it is already a 1.7x release. ========= Upgrade working copy This will upgrade your working copy to the new 1.7 format and make it unusable for older clients etc etc [Upgrade the working copy to the new 1.7 format] [Cancel keep the current format] ============ The workspace was successfuly acessed by cygwin client svn, version 1.7.5 (r1336830) compiled Jun 27 2012, 15:27:52 I'm a bit confused why TortoiseSVN can't handle. I will probably go back as a binary search to find a TortoiseSVN that works.. this is such a high cost on users (already a large amount of money/development time used up. I'd happy donate an amount of money to get a fixed .svn standard format for the next decade..) Thank you for any tips Regards, Jon
