Rebuild docs for kiko's changes to install; cvs add an HTML file I missed last time.

author: gerv%gerv.net <> 2004-01-17 09:18:59 +0100
committer: gerv%gerv.net <> 2004-01-17 09:18:59 +0100
commit: 9cbb96250af25688c13299e87e4ed12d8371a1fb (patch)
tree: 2077ad2f29ada919c33aa7642bc69614cac1928e /docs
parent: 09763eb1eb5d0f9b5284edb08ce76b216b358cc5 (diff)
download: bugzilla-9cbb96250af25688c13299e87e4ed12d8371a1fb.tar.gz
bugzilla-9cbb96250af25688c13299e87e4ed12d8371a1fb.tar.xz
5 files changed, 174 insertions, 15 deletions
diff --git a/docs/html/Bugzilla-Guide.html b/docs/html/Bugzilla-Guide.html
index 69da237dc..b066c51d1 100644
--- a/docs/html/Bugzilla-Guide.html
+++ b/docs/html/Bugzilla-Guide.html
@@ -4546,7 +4546,7 @@ NAME="AEN871"
 >By now you have a fully functional Bugzilla, but what good are
       bugs if they're not annoying? To help make those bugs more annoying you
       can set up Bugzilla's automatic whining system to complain at engineers
-      which leave their bugs in the NEW state without triaging them.
+      which leave their bugs in the NEW or REOPENED state without triaging them.
       </P
 ><P
 >&#13;      This can be done by
@@ -9738,8 +9738,8 @@ HREF="#faq-email-testing"
 ><DT
 >A.4.3. <A
 HREF="#faq-email-whine"
->&#13;	    I want whineatnews.pl to whine at something different to only new
-	    bugs. How do I do it?
+>&#13;	    I want whineatnews.pl to whine at something other than new and
+	    reopened bugs. How do I do it?
 	  </A
 ></DT
 ><DT
@@ -10941,8 +10941,8 @@ NAME="faq-email-whine"
 ><B
 >A.4.3. </B
 >
-	    I want whineatnews.pl to whine at something different to only new
-	    bugs. How do I do it?
+	    I want whineatnews.pl to whine at something other than new and
+	    reopened bugs. How do I do it?
 	  </P
 ></DIV
 ><DIV
diff --git a/docs/html/extraconfig.html b/docs/html/extraconfig.html
index 1e89106d1..14a32397b 100644
--- a/docs/html/extraconfig.html
+++ b/docs/html/extraconfig.html
@@ -213,7 +213,7 @@ NAME="AEN871"
 >By now you have a fully functional Bugzilla, but what good are
       bugs if they're not annoying? To help make those bugs more annoying you
       can set up Bugzilla's automatic whining system to complain at engineers
-      which leave their bugs in the NEW state without triaging them.
+      which leave their bugs in the NEW or REOPENED state without triaging them.
       </P
 ><P
 >&#13;      This can be done by
diff --git a/docs/html/faq.html b/docs/html/faq.html
index 93d8f717a..b5521816a 100644
--- a/docs/html/faq.html
+++ b/docs/html/faq.html
@@ -320,8 +320,8 @@ HREF="faq.html#faq-email-testing"
 ><DT
 >A.4.3. <A
 HREF="faq.html#faq-email-whine"
->&#13;	    I want whineatnews.pl to whine at something different to only new
-	    bugs. How do I do it?
+>&#13;	    I want whineatnews.pl to whine at something other than new and
+	    reopened bugs. How do I do it?
 	  </A
 ></DT
 ><DT
@@ -1523,8 +1523,8 @@ NAME="faq-email-whine"
 ><B
 >A.4.3. </B
 >
-	    I want whineatnews.pl to whine at something different to only new
-	    bugs. How do I do it?
+	    I want whineatnews.pl to whine at something other than new and
+	    reopened bugs. How do I do it?
 	  </P
 ></DIV
 ><DIV
diff --git a/docs/html/using-intro.html b/docs/html/using-intro.html
new file mode 100644
index 000000000..f9b0b6dd5
--- /dev/null
+++ b/docs/html/using-intro.html
@@ -0,0 +1,158 @@
+<HTML
+><HEAD
+><TITLE
+>Introduction</TITLE
+><META
+NAME="GENERATOR"
+CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
+"><LINK
+REL="HOME"
+TITLE="The Bugzilla Guide - 2.17.5 
+    Development Release"
+HREF="index.html"><LINK
+REL="UP"
+TITLE="Using Bugzilla"
+HREF="using.html"><LINK
+REL="PREVIOUS"
+TITLE="Using Bugzilla"
+HREF="using.html"><LINK
+REL="NEXT"
+TITLE="Create a Bugzilla Account"
+HREF="myaccount.html"></HEAD
+><BODY
+CLASS="section"
+BGCOLOR="#FFFFFF"
+TEXT="#000000"
+LINK="#0000FF"
+VLINK="#840084"
+ALINK="#0000FF"
+><DIV
+CLASS="NAVHEADER"
+><TABLE
+SUMMARY="Header navigation table"
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TH
+COLSPAN="3"
+ALIGN="center"
+>The Bugzilla Guide - 2.17.5 
+    Development Release</TH
+></TR
+><TR
+><TD
+WIDTH="10%"
+ALIGN="left"
+VALIGN="bottom"
+><A
+HREF="using.html"
+ACCESSKEY="P"
+>Prev</A
+></TD
+><TD
+WIDTH="80%"
+ALIGN="center"
+VALIGN="bottom"
+>Chapter 3. Using Bugzilla</TD
+><TD
+WIDTH="10%"
+ALIGN="right"
+VALIGN="bottom"
+><A
+HREF="myaccount.html"
+ACCESSKEY="N"
+>Next</A
+></TD
+></TR
+></TABLE
+><HR
+ALIGN="LEFT"
+WIDTH="100%"></DIV
+><DIV
+CLASS="section"
+><H1
+CLASS="section"
+><A
+NAME="using-intro"
+></A
+>3.1. Introduction</H1
+><P
+>This section contains information for end-users of Bugzilla. 
+    There is a Bugzilla test installation, called 
+    <A
+HREF="http://landfill.bugzilla.org/bugzilla-tip/"
+TARGET="_top"
+>Landfill</A
+>, 
+    which you are welcome to play with (if it's up.) 
+    However, it does not necessarily
+    have all Bugzilla features enabled, and runs an up-to-the-minute version, 
+    so some things may not quite work as this document describes.</P
+></DIV
+><DIV
+CLASS="NAVFOOTER"
+><HR
+ALIGN="LEFT"
+WIDTH="100%"><TABLE
+SUMMARY="Footer navigation table"
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+><A
+HREF="using.html"
+ACCESSKEY="P"
+>Prev</A
+></TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+><A
+HREF="index.html"
+ACCESSKEY="H"
+>Home</A
+></TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+><A
+HREF="myaccount.html"
+ACCESSKEY="N"
+>Next</A
+></TD
+></TR
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+>Using Bugzilla</TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+><A
+HREF="using.html"
+ACCESSKEY="U"
+>Up</A
+></TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+>Create a Bugzilla Account</TD
+></TR
+></TABLE
+></DIV
+></BODY
+></HTML
+>
+\ No newline at end of file
diff --git a/docs/txt/Bugzilla-Guide.txt b/docs/txt/Bugzilla-Guide.txt
index b4c4026bc..4cab77b9b 100644
--- a/docs/txt/Bugzilla-Guide.txt
+++ b/docs/txt/Bugzilla-Guide.txt
@@ -1344,7 +1344,8 @@ proc filter_deny { why } {
    By now you have a fully functional Bugzilla, but what good are bugs if
    they're not annoying? To help make those bugs more annoying you can
    set up Bugzilla's automatic whining system to complain at engineers
-   which leave their bugs in the NEW state without triaging them.
+   which leave their bugs in the NEW or REOPENED state without triaging
+   them.
 
    This can be done by adding the following command as a daily crontab
    entry (for help on that see that crontab man page):
@@ -3218,8 +3219,8 @@ Appendix A. The Bugzilla FAQ
         A.4.2. I'm evaluating/testing Bugzilla, and don't want it to send
                 email to anyone but me. How do I do it? 
 
-        A.4.3. I want whineatnews.pl to whine at something different to
-                only new bugs. How do I do it? 
+        A.4.3. I want whineatnews.pl to whine at something other than new
+                and reopened bugs. How do I do it? 
 
         A.4.4. How do I set up the email interface to submit/change bugs
                 via email? 
@@ -3561,8 +3562,8 @@ perl -pi -e 's@#\!/usr/bin/perl@#\!/usr/local/bin/perl@' *cgi *pl
    Edit the "newchangedmail" Param. Replace "To:" with "X-Real-To:",
    replace "Cc:" with "X-Real-CC:", and add a "To: <youremailaddress>".
 
-   A.4.3. I want whineatnews.pl to whine at something different to only
-   new bugs. How do I do it?
+   A.4.3. I want whineatnews.pl to whine at something other than new and
+   reopened bugs. How do I do it?
 
    Try Klaas Freitag's excellent patch for "whineatassigned"
    functionality. You can find it in bug 6679. This patch is against an
author	gerv%gerv.net <>	2004-01-17 09:18:59 +0100
committer	gerv%gerv.net <>	2004-01-17 09:18:59 +0100
commit	9cbb96250af25688c13299e87e4ed12d8371a1fb (patch)
tree	2077ad2f29ada919c33aa7642bc69614cac1928e /docs
parent	09763eb1eb5d0f9b5284edb08ce76b216b358cc5 (diff)
download	bugzilla-9cbb96250af25688c13299e87e4ed12d8371a1fb.tar.gz bugzilla-9cbb96250af25688c13299e87e4ed12d8371a1fb.tar.xz