Re: Which is the best tool /process to migrate VSS (with history) to Subversion

2016-06-20 Thread pjaytycy
> Unless you have a compelling need for history, I'd suggest you do a > simple export o a working copy from VSS to a simple export in > Subversiont. > I would argue to keep the history. It's very frustrating if 50+% of the times you use blame (to hopefully get some reasoning / context for a

1.6 dump => 1.5 load => dump => 1.8 load : any issues expected?

2015-09-28 Thread pjaytycy
Hello, We are planning to migrate our internal SVN servers. We are currently running on svn 1.6 on the server. We will get new infrastructure with SVN 1.5 server setup in the short term and are planning to upgrade to 1.8 at a later date. We are planning to do a dump from our current 1.6 server

Re: Attmpting to Update Working Directory for a Project from V1.6.17 to V1.7.1 using SVN Upgrade working copy

2011-12-05 Thread pjaytycy
Maybe this can happen in this specific situation if somebody uses "map network path" to a drive letter on windows. If the real root of the WC is \\someserver\\some\path\to\wc\root I can probably still map a drive letter (ie V: to \\someserver\some\path\to\wc\root\sub\folder\for\my\project If I th

extreme svn slowdown due to X-forwarding timeouts

2010-12-06 Thread pjaytycy
Hello, we recently upgraded svn on our remote build server from 1.5 to 1.6. This caused a drastic reduction in speed: u...@server:~$ time svn log -l 25 -q https:// [… snip …] real0m22.745s user0m0.192s sys 0m0.048s After some debugging, we found the cause to be entirely on my windo