From 09d0f35f2a00174b21266ec756d27dab87f468b2 Mon Sep 17 00:00:00 2001
From: Johnny Willemsen <jwillemsen@remedy.nl>
Date: Mon, 4 Dec 2006 12:52:14 +0000
Subject:

---
 ACE/docs/bczar/bczar.html      | 8 +++++---
 ACE/docs/bczar/privileges.html | 8 +++++---
 2 files changed, 10 insertions(+), 6 deletions(-)
diff --git a/ACE/docs/bczar/bczar.html b/ACE/docs/bczar/bczar.html
index dbe3bf5a53f..d7f652acfa9 100644
--- a/ACE/docs/bczar/bczar.html
+++ b/ACE/docs/bczar/bczar.html
@@ -1,3 +1,5 @@
+<!-- $Id$ -->
+
 <html>
 <head>
 <title>The realm of the build czar</title>
@@ -102,7 +104,7 @@ part of the release.</li>
 The best place to create the workspace is under /export/anduriltmp/bczar. Don't use
 the home directory itself, it is an NFS share and not really fast.
 </li>
-<li>Checkout like this: 
+<li>Checkout like this:
 <ul><li>svn co https://svn.dre.vanderbilt.edu/DOC/Middleware/trunk DOC_ROOT</li>
     <li>svn co https://svn.dre.vanderbilt.edu/DOC/MPC/trunk DOC_ROOT/ACE/MPC</li>
 </ul>
@@ -118,7 +120,7 @@ is used to fill the mail id portion of the ChangeLog entry.</li>
 <li> Change directories to to <tt>$DOC_ROOT</tt> </li>
 <li> Tag the release by executing <code>ACE/bin/make_release -v beta -u</code> This will only
 take a couple minutes to complete.</li>
-<li> Create the kits by executing <code>ACE/bin/make_release -k ace+tao+ciao </code> 
+<li> Create the kits by executing <code>ACE/bin/make_release -k ace+tao+ciao </code>
 
 <ul><li>These commands only tags and creates the kits for the
  software itself, not documentation. </li>
@@ -168,7 +170,7 @@ svn rm https://svn.dre.vanderbilt.edu/DOC/Middleware/tags/ACE+TAO+CIAO-X_Y_Z<br
 
 Note that this <em>only</em> needs to be done if the <em>tagging</em> fails.  If kit creation
 fails, simply restart that process.
-<li>The packages and up by default under /export/doc/latest, you can copy them to the webserver using the following commands. At the moment 
+<li>The packages and up by default under /export/doc/latest, you can copy them to the webserver using the following commands. At the moment
 you execute these commands all users can download these packages.</li>
 <code>
 cp /export/doc/latest/ACE* /export/www/download.dre/ACE+TAO-distribution<br>
diff --git a/ACE/docs/bczar/privileges.html b/ACE/docs/bczar/privileges.html
index 38bd3f26c35..299b88c299f 100644
--- a/ACE/docs/bczar/privileges.html
+++ b/ACE/docs/bczar/privileges.html
@@ -1,3 +1,5 @@
+<!-- $Id$ -->
+
 <html>
 <head>
 <title> Build Czar powers </title>
@@ -9,7 +11,7 @@
   failure to do so may result in some form of revolution
   (picture a firing squad).
   </P>
-  
+
   <P>
   Previous generations of the honorable royal family have automated
   the build process as much as possible, but all machines require attention:
@@ -38,7 +40,7 @@
     if needed.
   </P>
   <P>The build Czar should also investigate the errors and warnings
-    reported by a build, 
+    reported by a build,
     contact the person or persons responsible for the failed build and
     prompt them to fix the situation. If that process above fails the
     build Czar should  request help from a volunteer or proceed to fix
@@ -47,7 +49,7 @@
     forced to excomunicate the original developer and report him or
     her to the highest court of the land for whatever punishment is
     deemed appropriate (lashing or bone breaking where not prohibited
-    by law). 
+    by law).
   </P>
   <P>It is extremely important to fix broken builds within the day,
     otherwise the errors tend to accumulate and once the process
-- 
cgit v1.2.1

