From a75089f6734a71e5f90f3a4c5434fdc9c82ba5b9 Mon Sep 17 00:00:00 2001
From: Johnny Willemsen <jwillemsen@remedy.nl>
Date: Wed, 4 Oct 2006 08:41:54 +0000
Subject: small updates

---
 ACE/docs/bczar/bczar.html | 7 +++++--
 1 file changed, 5 insertions(+), 2 deletions(-)

diff --git a/ACE/docs/bczar/bczar.html b/ACE/docs/bczar/bczar.html
index a396ae53cae..0f2a4704add 100644
--- a/ACE/docs/bczar/bczar.html
+++ b/ACE/docs/bczar/bczar.html
@@ -28,7 +28,7 @@
 
   <li> Some tests fail in the daily builds for many reasons like known
   bugs, transient timeouts etc. Make sure that no new test failures
-  show up. This <a href="mailto:bala@cs.wustl.edu"> guy </a> knows
+  show up. This <a href="mailto:jwillemsen@remedy.nl"> guy </a> knows
   most of the information. Ask him to help you out with known
   problems.
 
@@ -66,7 +66,10 @@ step by step instructions on how to do that. </P>
 <P> The build czar can get the build configuration by looking at the
 config portion of the scoreboard </P>
 
-<p>Any pro-active involvement by the build czar is welcomed.</p>
+<p>Any pro-active involvement by the build czar is welcomed. Being
+a pro-active build czar will mean that you watch the subversion archive
+carefully and respond quickly to suspected changes. At the end it will
+safe time because the repo stays stable.</p>
 
 <hr>
 <h2>Recipe for Cutting a Beta/Minor Kit</h2>
-- 
cgit v1.2.1