[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: New (1.5) feature questions -- things we need to address before a release can happen

From: Blair Zajac <blair_at_orcaware.com>
Date: 2007-10-24 18:25:41 CEST

David Summers wrote:
> A thread got started this last May about "things we need to address
> before a release can happen."
> One of those is something that I run into sporadically (happened again
> today).
> There was discussion about it at
> http://svn.haxx.se/dev/archive-2007-05/0404.shtml
> but then the thread died.
> When a large commit happens to the slave server (re-directed to the
> master via web-dav proxy) then sometimes for a long time (1.5 hours this
> last time) the user got errors on his client (I can get the exact error
> if people are interested) until the slave synced up with the master
> repository.

In this case, don't you want to have the post-commit script block until it
brings all the mirrors up to date with svnsync? This is in contrast to the
normal situation where redirect std* to get their background processes to detach
from post-commit.


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Oct 24 18:26:03 2007

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.