From 5159ae5142a63c13992b335e33ad347adaa3ac70 Mon Sep 17 00:00:00 2001
From: "jocuri%softhome.net" <>
Date: Sun, 2 Nov 2003 22:04:28 +0000
Subject: Rebuilding documentation for the 2.17.5 release; the docbook system
 on landfill proved to be broken.

---
 docs/html/how.html | 59 +++++++++++++++++++++++++++++++++++++++---------------
 1 file changed, 43 insertions(+), 16 deletions(-)

(limited to 'docs/html/how.html')

diff --git a/docs/html/how.html b/docs/html/how.html
index fad287977..9b0f26f48 100644
--- a/docs/html/how.html
+++ b/docs/html/how.html
@@ -4,8 +4,7 @@
 >How do I use Bugzilla?</TITLE
 ><META
 NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
-"><LINK
+CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
 REL="HOME"
 TITLE="The Bugzilla Guide - 2.17.5 Development Release"
 HREF="index.html"><LINK
@@ -73,7 +72,9 @@ CLASS="section"
 ><H1
 CLASS="section"
 ><A
-NAME="how">3.1. How do I use Bugzilla?</H1
+NAME="how"
+></A
+>3.1. How do I use Bugzilla?</H1
 ><P
 >This section contains information for end-users of Bugzilla. 
     There is a Bugzilla test installation, called 
@@ -92,7 +93,9 @@ CLASS="section"
 ><H2
 CLASS="section"
 ><A
-NAME="myaccount">3.1.1. Create a Bugzilla Account</H2
+NAME="myaccount"
+></A
+>3.1.1. Create a Bugzilla Account</H2
 ><P
 >If you want to use Bugzilla, first you need to create an account.
       Consult with the administrator responsible for your installation of
@@ -160,7 +163,9 @@ CLASS="section"
 ><H2
 CLASS="section"
 ><A
-NAME="bug_page">3.1.2. Anatomy of a Bug</H2
+NAME="bug_page"
+></A
+>3.1.2. Anatomy of a Bug</H2
 ><P
 >The core of Bugzilla is the screen which displays a particular
       bug. It's a good place to explain some Bugzilla concepts. 
@@ -425,7 +430,9 @@ CLASS="section"
 ><H2
 CLASS="section"
 ><A
-NAME="query">3.1.3. Searching for Bugs</H2
+NAME="query"
+></A
+>3.1.3. Searching for Bugs</H2
 ><P
 >The Bugzilla Search page is is the interface where you can find
       any bug report, comment, or patch currently in the Bugzilla system. You
@@ -453,7 +460,9 @@ CLASS="section"
 ><H2
 CLASS="section"
 ><A
-NAME="list">3.1.4. Bug Lists</H2
+NAME="list"
+></A
+>3.1.4. Bug Lists</H2
 ><P
 >If you run a search, a list of matching bugs will be returned.
       The default search is to return all open bugs on the system - don't try
@@ -525,7 +534,9 @@ CLASS="section"
 ><H2
 CLASS="section"
 ><A
-NAME="bugreports">3.1.5. Filing Bugs</H2
+NAME="bugreports"
+></A
+>3.1.5. Filing Bugs</H2
 ><P
 >Years of bug writing experience has been distilled for your
       reading pleasure into the 
@@ -583,7 +594,9 @@ CLASS="section"
 ><H2
 CLASS="section"
 ><A
-NAME="patchviewer">3.1.6. Patch Viewer</H2
+NAME="patchviewer"
+></A
+>3.1.6. Patch Viewer</H2
 ><P
 >Viewing and reviewing patches in Bugzilla is often difficult due to
       lack of context, improper format and the inherent readability issues that
@@ -639,7 +652,9 @@ CLASS="section"
 ><H3
 CLASS="section"
 ><A
-NAME="patchviewer_view">3.1.6.1. Viewing Patches in Patch Viewer</H3
+NAME="patchviewer_view"
+></A
+>3.1.6.1. Viewing Patches in Patch Viewer</H3
 ><P
 >The main way to view a patch in patch viewer is to click on the
         "Diff" link next to a patch in the Attachments list on a bug. You may
@@ -651,7 +666,9 @@ CLASS="section"
 ><H3
 CLASS="section"
 ><A
-NAME="patchviewer_diff">3.1.6.2. Seeing the Difference Between Two Patches</H3
+NAME="patchviewer_diff"
+></A
+>3.1.6.2. Seeing the Difference Between Two Patches</H3
 ><P
 >To see the difference between two patches, you must first view the
         newer patch in Patch Viewer.  Then select the older patch from the
@@ -664,7 +681,9 @@ CLASS="section"
 ><H3
 CLASS="section"
 ><A
-NAME="patchviewer_context">3.1.6.3. Getting More Context in a Patch</H3
+NAME="patchviewer_context"
+></A
+>3.1.6.3. Getting More Context in a Patch</H3
 ><P
 >To get more context in a patch, you put a number in the textbox at
         the top of Patch Viewer ("Patch / File / [textbox]") and hit enter.
@@ -678,7 +697,9 @@ CLASS="section"
 ><H3
 CLASS="section"
 ><A
-NAME="patchviewer_collapse">3.1.6.4. Collapsing and Expanding Sections of a Patch</H3
+NAME="patchviewer_collapse"
+></A
+>3.1.6.4. Collapsing and Expanding Sections of a Patch</H3
 ><P
 >To view only a certain set of files in a patch (for example, if a
         patch is absolutely huge and you want to only review part of it at a
@@ -692,7 +713,9 @@ CLASS="section"
 ><H3
 CLASS="section"
 ><A
-NAME="patchviewer_link">3.1.6.5. Linking to a Section of a Patch</H3
+NAME="patchviewer_link"
+></A
+>3.1.6.5. Linking to a Section of a Patch</H3
 ><P
 >To link to a section of a patch (for example, if you want to be
         able to give someone a URL to show them which part you are talking
@@ -705,7 +728,9 @@ CLASS="section"
 ><H3
 CLASS="section"
 ><A
-NAME="patchviewer_bonsai_lxr">3.1.6.6. Going to Bonsai and LXR</H3
+NAME="patchviewer_bonsai_lxr"
+></A
+>3.1.6.6. Going to Bonsai and LXR</H3
 ><P
 >To go to Bonsai to get blame for the lines you are interested in,
         you can click the "Lines XX-YY" link on the section header you are
@@ -721,7 +746,9 @@ CLASS="section"
 ><H3
 CLASS="section"
 ><A
-NAME="patchviewer_unified_diff">3.1.6.7. Creating a Unified Diff</H3
+NAME="patchviewer_unified_diff"
+></A
+>3.1.6.7. Creating a Unified Diff</H3
 ><P
 >If the patch is not in a format that you like, you can turn it
         into a unified diff format by clicking the "Raw Unified" link at the top
-- 
cgit v1.2.3-24-g4f1b