Thanks Andy. I could probably have my company wait 2-3 months, probably
not half a year.
You know, as svn is merge and not lock based, everybody in my department
needs to do an update
before modifying anything, so it is a medium problem for us.
So what can I do in order to accelerate the svn update for my repository.
I dont want svn being so slow as it can be replaced by sourcesafe or
something else if perceived as a problem.
Could you explain further on why is svn update slow for large
repositories, so I can do a workaround
in the meanwhile. Does it depends on large files, lot of files, large,
commits, or what ? Can I apply
a 1.4 patch for my 1.2.3 installation ?
Thanks for your time.
Andy Levy wrote:
>On 12/8/05, Daniel Montero <danim@soin.co.cr> wrote:
>
>
>> Giovanni, thanks for your reply.
>>
>> Is there anything I could do to workaround this. I can't find any 1.4
>>version, even in the sourcecode. What fix should I apply in order to get
>>this working ?
>> Or, perhaps, when is 1.4 scheduled ? I had not found that on the website.
>>
>>
>
>The final release candidate for 1.3 was just released this past week.
>Based on that, 1.4 is going to be sometime in 2006 at least. It's
>probably too early to schedule a release date just yet.
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
>For additional commands, e-mail: users-help@subversion.tigris.org
>
>
>
>
Received on Thu Dec 8 17:22:19 2005