Latest version of compiled docs (picking up recent SGML changes).

git-svn-id: svn://10.0.0.236/trunk@112476 18797224-902f-48f8-a5cc-f745e15eee43
This commit is contained in:
jake%acutex.net
2002-01-18 23:27:01 +00:00
parent b3500ab834
commit d84d21016e
70 changed files with 8661 additions and 5243 deletions

View File

@@ -19,7 +19,7 @@ REL="NEXT"
TITLE="Copyright Information"
HREF="copyright.html"></HEAD
><BODY
CLASS="SECTION"
CLASS="section"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
@@ -66,28 +66,28 @@ HREF="copyright.html"
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="SECTION"
CLASS="section"
><H1
CLASS="SECTION"
CLASS="section"
><A
NAME="ABOUTTHISGUIDE"
NAME="aboutthisguide"
>1.1. Purpose and Scope of this Guide</A
></H1
><P
> This document was started on September 17, 2000 by Matthew P.
>&#13; This document was started on September 17, 2000 by Matthew P.
Barnson after a great deal of procrastination updating the
Bugzilla FAQ, which I left untouched for nearly half a year.
After numerous complete rewrites and reformatting, it is the
document you see today.
</P
><P
> Bugzilla is simply the best piece of bug-tracking software the
>&#13; Bugzilla is simply the best piece of bug-tracking software the
world has ever seen. This document is intended to be the
comprehensive guide to the installation, administration,
maintenance, and use of the Bugzilla bug-tracking system.
</P
><P
> This release of the Bugzilla Guide is the
>&#13; This release of the Bugzilla Guide is the
<EM
>2.14</EM
> release. It is so named that it
@@ -108,7 +108,7 @@ NAME="ABOUTTHISGUIDE"
developers, and those who enjoy a lot of pain.
</P
><P
> Newer revisions of the Bugzilla Guide follow the numbering
>&#13; Newer revisions of the Bugzilla Guide follow the numbering
conventions of the main-tree Bugzilla releases, available at
<A
HREF="http://www.mozilla.org/projects/bugzilla"
@@ -123,13 +123,13 @@ TARGET="_top"
Got it? Good.
</P
><P
> I wrote this in response to the enormous demand for decent
>&#13; I wrote this in response to the enormous demand for decent
Bugzilla documentation. I have incorporated instructions from
the Bugzilla README, Frequently Asked Questions, Database Schema
Document, and various mailing lists to create it. Chances are,
there are glaring errors in this documentation; please contact
<TT
CLASS="EMAIL"
CLASS="email"
>&#60;<A
HREF="mailto:barnboy@trilobyte.net"
>barnboy@trilobyte.net</A