Skip to content

bugzilla
bugzilla
Commit 96a0037a authored by gerv%gerv.net's avatar gerv%gerv.net
Browse files
Options

Another pre-2.17.7 rev.

parent cb5afb1e
Expand all Hide whitespace changes
Inline Side-by-side
Showing with 252 additions and 277 deletions
docs/html/bug_page.html
View file @ 96a0037a
......@@ -77,7 +77,7 @@ CLASS="section"
><A
NAME="bug_page"
></A
>3.2. Anatomy of a Bug</H1
>3.3. Anatomy of a Bug</H1
><P
>The core of Bugzilla is the screen which displays a particular
bug. It's a good place to explain some Bugzilla concepts.
......
docs/html/bugreports.html
View file @ 96a0037a
......@@ -77,7 +77,7 @@ CLASS="section"
><A
NAME="bugreports"
></A
>3.5. Filing Bugs</H1
>3.6. Filing Bugs</H1
><P
>Years of bug writing experience has been distilled for your
reading pleasure into the
......@@ -129,6 +129,22 @@ TARGET="_top"
>Select "Commit" and send in your bug report.</P
></LI
></OL
><P
>Try to make sure that everything said in the summary is also
said in the first comment. Summaries are often updated and this will
ensure your original information is easily accessible.
</P
><P
>&#13; You do not need to put "any" or similar strings in the URL field.
If there is no specific URL associated with the bug, leave this
field blank.
</P
><P
>If you feel a bug you filed was incorrectly marked as a
DUPLICATE of another, please question it in your bug, not
the bug it was duped to. Feel free to CC the person who duped it
if they are not already CCed.
</P
></DIV
><DIV
CLASS="NAVFOOTER"
......
docs/html/conventions.html
View file @ 96a0037a
......@@ -83,7 +83,7 @@ NAME="conventions"
><DIV
CLASS="informaltable"
><A
NAME="AEN73"
NAME="AEN72"
></A
><P
></P
......@@ -107,7 +107,7 @@ VALIGN="MIDDLE"
><TD
ALIGN="LEFT"
VALIGN="MIDDLE"
>Warnings</TD
>Warning</TD
><TD
ALIGN="LEFT"
VALIGN="MIDDLE"
......@@ -181,7 +181,7 @@ VALIGN="TOP"
><TD
ALIGN="LEFT"
VALIGN="MIDDLE"
>Notes</TD
>Note</TD
><TD
ALIGN="LEFT"
VALIGN="MIDDLE"
......@@ -255,7 +255,7 @@ VALIGN="TOP"
><TD
ALIGN="LEFT"
VALIGN="MIDDLE"
>File and directory names</TD
>File or directory name</TD
><TD
ALIGN="LEFT"
VALIGN="MIDDLE"
......@@ -269,7 +269,7 @@ CLASS="filename"
><TD
ALIGN="LEFT"
VALIGN="MIDDLE"
>Commands to be typed</TD
>Command to be typed</TD
><TD
ALIGN="LEFT"
VALIGN="MIDDLE"
......@@ -283,7 +283,7 @@ CLASS="command"
><TD
ALIGN="LEFT"
VALIGN="MIDDLE"
>Applications names</TD
>Application name</TD
><TD
ALIGN="LEFT"
VALIGN="MIDDLE"
......@@ -297,12 +297,7 @@ CLASS="application"
><TD
ALIGN="LEFT"
VALIGN="MIDDLE"
>&#13; <I
CLASS="foreignphrase"
>Prompt</I
>
of users command under bash shell</TD
>&#13; Normal user's prompt under bash shell</TD
><TD
ALIGN="LEFT"
VALIGN="MIDDLE"
......@@ -312,12 +307,7 @@ VALIGN="MIDDLE"
><TD
ALIGN="LEFT"
VALIGN="MIDDLE"
>&#13; <I
CLASS="foreignphrase"
>Prompt</I
>
of root users command under bash shell</TD
>&#13; Root user's prompt under bash shell</TD
><TD
ALIGN="LEFT"
VALIGN="MIDDLE"
......@@ -327,12 +317,7 @@ VALIGN="MIDDLE"
><TD
ALIGN="LEFT"
VALIGN="MIDDLE"
>&#13; <I
CLASS="foreignphrase"
>Prompt</I
>
of user command under tcsh shell</TD
>&#13; Normal user's prompt under tcsh shell</TD
><TD
ALIGN="LEFT"
VALIGN="MIDDLE"
......
docs/html/credits.html
View file @ 96a0037a
......@@ -90,7 +90,7 @@ NAME="credits"
><P
>&#13; Last but not least, all the members of the
<A
HREF="news://news.mozilla.org/netscape/public/mozilla/webtools"
HREF="news://news.mozilla.org/netscape.public.mozilla.webtools"
TARGET="_top"
>&#13; netscape.public.mozilla.webtools</A
>
......
docs/html/cust-templates.html
View file @ 96a0037a
......@@ -97,7 +97,7 @@ CLASS="section"
><H2
CLASS="section"
><A
NAME="AEN1597"
NAME="AEN1588"
></A
>6.1.1. What to Edit</H2
><P
......@@ -249,7 +249,7 @@ CLASS="section"
><H2
CLASS="section"
><A
NAME="AEN1620"
NAME="AEN1611"
></A
>6.1.2. How To Edit Templates</H2
><DIV
......@@ -329,7 +329,7 @@ CLASS="section"
><H2
CLASS="section"
><A
NAME="AEN1630"
NAME="AEN1621"
></A
>6.1.3. Template Formats</H2
><P
......@@ -391,7 +391,7 @@ CLASS="section"
><H2
CLASS="section"
><A
NAME="AEN1643"
NAME="AEN1634"
></A
>6.1.4. Particular Templates</H2
><P
......
docs/html/customization.html
View file @ 96a0037a
......@@ -90,22 +90,22 @@ HREF="cust-templates.html"
><DL
><DT
>6.1.1. <A
HREF="cust-templates.html#AEN1597"
HREF="cust-templates.html#AEN1588"
>What to Edit</A
></DT
><DT
>6.1.2. <A
HREF="cust-templates.html#AEN1620"
HREF="cust-templates.html#AEN1611"
>How To Edit Templates</A
></DT
><DT
>6.1.3. <A
HREF="cust-templates.html#AEN1630"
HREF="cust-templates.html#AEN1621"
>Template Formats</A
></DT
><DT
>6.1.4. <A
HREF="cust-templates.html#AEN1643"
HREF="cust-templates.html#AEN1634"
>Particular Templates</A
></DT
><DT
......
docs/html/dbdoc.html
View file @ 96a0037a
......@@ -137,7 +137,7 @@ CLASS="section"
><H2
CLASS="section"
><A
NAME="AEN1719"
NAME="AEN1710"
></A
>6.4.1. Bugzilla Database Basics</H2
><P
......@@ -251,7 +251,7 @@ CLASS="section"
><H3
CLASS="section"
><A
NAME="AEN1746"
NAME="AEN1737"
></A
>6.4.1.1. Bugzilla Database Tables</H3
><P
......
docs/html/extraconfig.html
View file @ 96a0037a
......@@ -83,7 +83,7 @@ CLASS="section"
><H2
CLASS="section"
><A
NAME="AEN852"
NAME="AEN843"
></A
>4.3.1. Dependency Charts</H2
><P
......@@ -147,7 +147,7 @@ CLASS="section"
><H2
CLASS="section"
><A
NAME="AEN867"
NAME="AEN858"
></A
>4.3.2. Bug Graphs</H2
><P
......@@ -206,7 +206,7 @@ CLASS="section"
><H2
CLASS="section"
><A
NAME="AEN880"
NAME="AEN871"
></A
>4.3.3. The Whining Cron</H2
><P
......
docs/html/faq.html
View file @ 96a0037a
......@@ -1974,7 +1974,7 @@ CLASS="answer"
><P
>&#13; Microsoft has some advice on this matter, as well:
<A
NAME="AEN2062"
NAME="AEN2053"
></A
><BLOCKQUOTE
CLASS="BLOCKQUOTE"
......
docs/html/gfdl-howto.html
View file @ 96a0037a
......@@ -83,7 +83,7 @@ NAME="gfdl-howto"
of the License in the document and put the following copyright and
license notices just after the title page:</P
><A
NAME="AEN2282"
NAME="AEN2273"
></A
><BLOCKQUOTE
CLASS="BLOCKQUOTE"
......
docs/html/gfdl.html
View file @ 96a0037a
......@@ -146,7 +146,7 @@ HREF="gfdl-howto.html"
><P
>Version 1.1, March 2000</P
><A
NAME="AEN2192"
NAME="AEN2183"
></A
><BLOCKQUOTE
CLASS="BLOCKQUOTE"
......
docs/html/glossary.html
View file @ 96a0037a
......@@ -72,7 +72,7 @@ CLASS="glossdiv"
><H1
CLASS="glossdiv"
><A
NAME="AEN2287"
NAME="AEN2278"
></A
>0-9, high ascii</H1
><DL
......@@ -936,7 +936,7 @@ NAME="gloss-zarro"
Terry had the following to say:
</P
><A
NAME="AEN2522"
NAME="AEN2513"
></A
><TABLE
BORDER="0"
......
docs/html/hintsandtips.html
View file @ 96a0037a
......@@ -77,7 +77,7 @@ CLASS="section"
><A
NAME="hintsandtips"
></A
>3.7. Hints and Tips</H1
>3.8. Hints and Tips</H1
><P
>This section distills some Bugzilla tips and best practices
that have been developed.</P
......@@ -86,9 +86,9 @@ CLASS="section"
><H2
CLASS="section"
><A
NAME="AEN358"
NAME="AEN363"
></A
>3.7.1. Autolinkification</H2
>3.8.1. Autolinkification</H2
><P
>Bugzilla comments are plain text - so typing &#60;U&#62; will
produce less-than, U, greater-than rather than underlined text.
......@@ -157,7 +157,7 @@ CLASS="section"
><A
NAME="quicksearch"
></A
>3.7.2. Quicksearch</H2
>3.8.2. Quicksearch</H2
><P
>Quicksearch is a single-text-box query tool which uses
metacharacters to indicate what is to be searched. For example, typing
......@@ -190,7 +190,7 @@ CLASS="section"
><A
NAME="commenting"
></A
>3.7.3. Comments</H2
>3.8.3. Comments</H2
><P
>If you are changing the fields on a bug, only comment if
either you have something pertinent to say, or Bugzilla requires it.
......@@ -214,7 +214,7 @@ CLASS="section"
><A
NAME="attachments"
></A
>3.7.4. Attachments</H2
>3.8.4. Attachments</H2
><P
>&#13; Use attachments, rather than comments, for large chunks of ASCII data,
such as trace, debugging output files, or log files. That way, it doesn't
......@@ -233,31 +233,6 @@ NAME="attachments"
out of the bug.
</P
></DIV
><DIV
CLASS="section"
><H2
CLASS="section"
><A
NAME="AEN388"
></A
>3.7.5. Filing Bugs</H2
><P
>Try to make sure that everything said in the summary is also
said in the first comment. Summaries are often updated and this will
ensure your original information is easily accessible.
</P
><P
>&#13; You do not need to put "any" or similar strings in the URL field.
If there is no specific URL associated with the bug, leave this
field blank.
</P
><P
>If you feel a bug you filed was incorrectly marked as a
DUPLICATE of another, please question it in your bug, not
the bug it was duped to. Feel free to CC the person who duped it
if they are not already CCed.
</P
></DIV
></DIV
><DIV
CLASS="NAVFOOTER"
......
docs/html/index.html
View file @ 96a0037a
......@@ -158,46 +158,51 @@ HREF="using.html"
><DL
><DT
>3.1. <A
HREF="using-intro.html"
>Introduction</A
></DT
><DT
>3.2. <A
HREF="myaccount.html"
>Create a Bugzilla Account</A
></DT
><DT
>3.2. <A
>3.3. <A
HREF="bug_page.html"
>Anatomy of a Bug</A
></DT
><DT
>3.3. <A
>3.4. <A
HREF="query.html"
>Searching for Bugs</A
></DT
><DT
>3.4. <A
>3.5. <A
HREF="list.html"
>Bug Lists</A
></DT
><DT
>3.5. <A
>3.6. <A
HREF="bugreports.html"
>Filing Bugs</A
></DT
><DT
>3.6. <A
>3.7. <A
HREF="patchviewer.html"
>Patch Viewer</A
></DT
><DT
>3.7. <A
>3.8. <A
HREF="hintsandtips.html"
>Hints and Tips</A
></DT
><DT
>3.8. <A
>3.9. <A
HREF="userpreferences.html"
>User Preferences</A
></DT
><DT
>3.9. <A
>3.10. <A
HREF="reporting.html"
>Reports</A
></DT
......
docs/html/installation.html
View file @ 96a0037a
......@@ -110,20 +110,20 @@ HREF="stepbystep.html#install-bzfiles"
></DT
><DT
>4.1.5. <A
HREF="stepbystep.html#install-perlmodules"
>Perl Modules</A
></DT
><DT
>4.1.6. <A
HREF="stepbystep.html#AEN748"
HREF="stepbystep.html#AEN522"
><TT
CLASS="filename"
>checksetup.pl</TT
></A
></DT
><DT
>4.1.6. <A
HREF="stepbystep.html#install-perlmodules"
>Perl Modules</A
></DT
><DT
>4.1.7. <A
HREF="stepbystep.html#AEN778"
HREF="stepbystep.html#AEN768"
>Configuring Bugzilla</A
></DT
></DL
......@@ -167,17 +167,17 @@ HREF="extraconfig.html"
><DL
><DT
>4.3.1. <A
HREF="extraconfig.html#AEN852"
HREF="extraconfig.html#AEN843"
>Dependency Charts</A
></DT
><DT
>4.3.2. <A
HREF="extraconfig.html#AEN867"
HREF="extraconfig.html#AEN858"
>Bug Graphs</A
></DT
><DT
>4.3.3. <A
HREF="extraconfig.html#AEN880"
HREF="extraconfig.html#AEN871"
>The Whining Cron</A
></DT
><DT
......@@ -276,12 +276,12 @@ HREF="troubleshooting.html"
><DL
><DT
>4.6.1. <A
HREF="troubleshooting.html#AEN1215"
HREF="troubleshooting.html#AEN1206"
>Bundle::Bugzilla makes me upgrade to Perl 5.6.1</A
></DT
><DT
>4.6.2. <A
HREF="troubleshooting.html#AEN1220"
HREF="troubleshooting.html#AEN1211"
>DBD::Sponge::db prepare failed</A
></DT
><DT
......
docs/html/list.html
View file @ 96a0037a
......@@ -77,7 +77,7 @@ CLASS="section"
><A
NAME="list"
></A
>3.4. Bug Lists</H1
>3.5. Bug Lists</H1
><P
>If you run a search, a list of matching bugs will be returned.
</P
......@@ -102,6 +102,15 @@ BORDER="0"
><TR
><TD
>&#13; <EM
>CSV:</EM
>
get the buglist as comma-separated values, for import into e.g.
a spreadsheet.</TD
></TR
><TR
><TD
>&#13; <EM
>Change Columns:</EM
>
......@@ -128,13 +137,23 @@ BORDER="0"
><TR
><TD
>&#13; <EM
>Edit this query:</EM
>Edit Search:</EM
>
If you didn't get exactly the results you were looking for, you can
return to the Query page through this link and make small revisions
to the query you just made so you get more accurate results.</TD
></TR
><TR
><TD
>&#13; <EM
>Remember Search As:</EM
>
You can give a search a name and remember it; a link will appear
in your page footer giving you quick access to run it again later.
</TD
></TR
></TBODY
></TABLE
><P
......
docs/html/myaccount.html
View file @ 96a0037a
......@@ -14,8 +14,8 @@ REL="UP"
TITLE="Using Bugzilla"
HREF="using.html"><LINK
REL="PREVIOUS"
TITLE="Using Bugzilla"
HREF="using.html"><LINK
TITLE="Introduction"
HREF="using-intro.html"><LINK
REL="NEXT"
TITLE="Anatomy of a Bug"
HREF="bug_page.html"></HEAD
......@@ -47,7 +47,7 @@ WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="using.html"
HREF="using-intro.html"
ACCESSKEY="P"
>Prev</A
></TD
......@@ -77,7 +77,7 @@ CLASS="section"
><A
NAME="myaccount"
></A
>3.1. Create a Bugzilla Account</H1
>3.2. Create a Bugzilla Account</H1
><P
>If you want to use Bugzilla, first you need to create an account.
Consult with the administrator responsible for your installation of
......@@ -156,7 +156,7 @@ WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="using.html"
HREF="using-intro.html"
ACCESSKEY="P"
>Prev</A
></TD
......@@ -184,7 +184,7 @@ ACCESSKEY="N"
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>Using Bugzilla</TD
>Introduction</TD
><TD
WIDTH="34%"
ALIGN="center"
......
docs/html/newversions.html
View file @ 96a0037a
......@@ -87,25 +87,23 @@ NAME="newversions"
</P
><P
>&#13; The newest version of this guide can always be found at <A
>&#13; The latest version of this guide can always be found at <A
HREF="http://www.bugzilla.org"
TARGET="_top"
>http://www.bugzilla.org</A
>; however, you should read the version
which came with the Bugzilla release you are using.
</P
><P
>&#13; The latest version of this document can always be checked out via CVS.
Please follow the <A
>, or checked out via CVS.
(Please follow the <A
HREF="http://www.mozilla.org/cvs.html"
TARGET="_top"
>Mozilla CVS</A
>
instructions and check out the <TT
>Mozilla
CVS</A
> instructions and check out the
<TT
CLASS="filename"
>mozilla/webtools/bugzilla/docs/</TT
>
subtree.
subtree.) However, you should read the version
which came with the Bugzilla release you are using.
</P
><P
>&#13; The Bugzilla Guide is currently only available in English.
......
docs/html/os-specific.html
View file @ 96a0037a
......@@ -152,7 +152,7 @@ NAME="win32-perlmodules"
>Bugzilla on Windows requires the same perl modules found in
<A
HREF="stepbystep.html#install-perlmodules"
>Section 4.1.5</A
>Section 4.1.6</A
>. The main difference is that
windows uses <A
HREF="glossary.html#gloss-ppm"
......
docs/html/patchviewer.html
View file @ 96a0037a
......@@ -77,7 +77,7 @@ CLASS="section"
><A
NAME="patchviewer"
></A
>3.6. Patch Viewer</H1
>3.7. Patch Viewer</H1
><P
>Viewing and reviewing patches in Bugzilla is often difficult due to
lack of context, improper format and the inherent readability issues that
......@@ -135,7 +135,7 @@ CLASS="section"
><A
NAME="patchviewer_view"
></A
>3.6.1. Viewing Patches in Patch Viewer</H2
>3.7.1. Viewing Patches in Patch Viewer</H2
><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
......@@ -149,7 +149,7 @@ CLASS="section"
><A
NAME="patchviewer_diff"
></A
>3.6.2. Seeing the Difference Between Two Patches</H2
>3.7.2. Seeing the Difference Between Two Patches</H2
><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
......@@ -164,7 +164,7 @@ CLASS="section"
><A
NAME="patchviewer_context"
></A
>3.6.3. Getting More Context in a Patch</H2
>3.7.3. Getting More Context in a Patch</H2
><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.
......@@ -180,7 +180,7 @@ CLASS="section"
><A
NAME="patchviewer_collapse"
></A
>3.6.4. Collapsing and Expanding Sections of a Patch</H2
>3.7.4. Collapsing and Expanding Sections of a Patch</H2
><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
......@@ -196,7 +196,7 @@ CLASS="section"
><A
NAME="patchviewer_link"
></A
>3.6.5. Linking to a Section of a Patch</H2
>3.7.5. Linking to a Section of a Patch</H2
><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
......@@ -211,7 +211,7 @@ CLASS="section"
><A
NAME="patchviewer_bonsai_lxr"
></A
>3.6.6. Going to Bonsai and LXR</H2
>3.7.6. Going to Bonsai and LXR</H2
><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
......@@ -229,7 +229,7 @@ CLASS="section"
><A
NAME="patchviewer_unified_diff"
></A
>3.6.7. Creating a Unified Diff</H2
>3.7.7. Creating a Unified Diff</H2
><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
......
docs/html/query.html
View file @ 96a0037a
......@@ -77,7 +77,7 @@ CLASS="section"
><A
NAME="query"
></A
>3.3. Searching for Bugs</H1
>3.4. Searching for Bugs</H1
><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
......
docs/html/reporting.html
View file @ 96a0037a
......@@ -77,7 +77,7 @@ CLASS="section"
><A
NAME="reporting"
></A
>3.9. Reports</H1
>3.10. Reports</H1
><P
><EM
>To be written</EM
......
docs/html/troubleshooting.html
View file @ 96a0037a
......@@ -87,7 +87,7 @@ CLASS="section"
><H2
CLASS="section"
><A
NAME="AEN1215"
NAME="AEN1206"
></A
>4.6.1. Bundle::Bugzilla makes me upgrade to Perl 5.6.1</H2
><P
......@@ -112,7 +112,7 @@ CLASS="section"
><H2
CLASS="section"
><A
NAME="AEN1220"
NAME="AEN1211"
></A
>4.6.2. DBD::Sponge::db prepare failed</H2
><P
......
docs/html/userpreferences.html
View file @ 96a0037a
......@@ -77,7 +77,7 @@ CLASS="section"
><A
NAME="userpreferences"
></A
>3.8. User Preferences</H1
>3.9. User Preferences</H1
><P
>Once you have logged in, you can customise various aspects of
Bugzilla via the "Edit prefs" link in the page footer.
......@@ -89,7 +89,7 @@ CLASS="section"
><A
NAME="accountsettings"
></A
>3.8.1. Account Settings</H2
>3.9.1. Account Settings</H2
><P
>On this tab, you can change your basic account information,
including your password, email address and real name. For security
......@@ -114,7 +114,7 @@ CLASS="section"
><A
NAME="emailsettings"
></A
>3.8.2. Email Settings</H2
>3.9.2. Email Settings</H2
><P
>On this tab you can reduce or increase the amount of email sent
you from Bugzilla, opting in our out depending on your relationship to
......@@ -169,7 +169,7 @@ CLASS="section"
><A
NAME="permissionsettings"
></A
>3.8.3. Permissions</H2
>3.9.3. Permissions</H2
><P
>This is a purely informative page which outlines your current
permissions on this installation of Bugzilla - what product groups you
......
docs/html/using.html
View file @ 96a0037a
......@@ -14,8 +14,8 @@ REL="PREVIOUS"
TITLE="Why use Bugzilla?"
HREF="why-bugzilla.html"><LINK
REL="NEXT"
TITLE="Create a Bugzilla Account"
HREF="myaccount.html"></HEAD
TITLE="Introduction"
HREF="using-intro.html"></HEAD
><BODY
CLASS="chapter"
BGCOLOR="#FFFFFF"
......@@ -58,7 +58,7 @@ WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="myaccount.html"
HREF="using-intro.html"
ACCESSKEY="N"
>Next</A
></TD
......@@ -83,150 +83,138 @@ CLASS="TOC"
></DT
><DT
>3.1. <A
HREF="using-intro.html"
>Introduction</A
></DT
><DT
>3.2. <A
HREF="myaccount.html"
>Create a Bugzilla Account</A
></DT
><DT
>3.2. <A
>3.3. <A
HREF="bug_page.html"
>Anatomy of a Bug</A
></DT
><DT
>3.3. <A
>3.4. <A
HREF="query.html"
>Searching for Bugs</A
></DT
><DT
>3.4. <A
>3.5. <A
HREF="list.html"
>Bug Lists</A
></DT
><DT
>3.5. <A
>3.6. <A
HREF="bugreports.html"
>Filing Bugs</A
></DT
><DT
>3.6. <A
>3.7. <A
HREF="patchviewer.html"
>Patch Viewer</A
></DT
><DD
><DL
><DT
>3.6.1. <A
>3.7.1. <A
HREF="patchviewer.html#patchviewer_view"
>Viewing Patches in Patch Viewer</A
></DT
><DT
>3.6.2. <A
>3.7.2. <A
HREF="patchviewer.html#patchviewer_diff"
>Seeing the Difference Between Two Patches</A
></DT
><DT
>3.6.3. <A
>3.7.3. <A
HREF="patchviewer.html#patchviewer_context"
>Getting More Context in a Patch</A
></DT
><DT
>3.6.4. <A
>3.7.4. <A
HREF="patchviewer.html#patchviewer_collapse"
>Collapsing and Expanding Sections of a Patch</A
></DT
><DT
>3.6.5. <A
>3.7.5. <A
HREF="patchviewer.html#patchviewer_link"
>Linking to a Section of a Patch</A
></DT
><DT
>3.6.6. <A
>3.7.6. <A
HREF="patchviewer.html#patchviewer_bonsai_lxr"
>Going to Bonsai and LXR</A
></DT
><DT
>3.6.7. <A
>3.7.7. <A
HREF="patchviewer.html#patchviewer_unified_diff"
>Creating a Unified Diff</A
></DT
></DL
></DD
><DT
>3.7. <A
>3.8. <A
HREF="hintsandtips.html"
>Hints and Tips</A
></DT
><DD
><DL
><DT
>3.7.1. <A
HREF="hintsandtips.html#AEN358"
>3.8.1. <A
HREF="hintsandtips.html#AEN363"
>Autolinkification</A
></DT
><DT
>3.7.2. <A
>3.8.2. <A
HREF="hintsandtips.html#quicksearch"
>Quicksearch</A
></DT
><DT
>3.7.3. <A
>3.8.3. <A
HREF="hintsandtips.html#commenting"
>Comments</A
></DT
><DT
>3.7.4. <A
>3.8.4. <A
HREF="hintsandtips.html#attachments"
>Attachments</A
></DT
><DT
>3.7.5. <A
HREF="hintsandtips.html#AEN388"
>Filing Bugs</A
></DT
></DL
></DD
><DT
>3.8. <A
>3.9. <A
HREF="userpreferences.html"
>User Preferences</A
></DT
><DD
><DL
><DT
>3.8.1. <A
>3.9.1. <A
HREF="userpreferences.html#accountsettings"
>Account Settings</A
></DT
><DT
>3.8.2. <A
>3.9.2. <A
HREF="userpreferences.html#emailsettings"
>Email Settings</A
></DT
><DT
>3.8.3. <A
>3.9.3. <A
HREF="userpreferences.html#permissionsettings"
>Permissions</A
></DT
></DL
></DD
><DT
>3.9. <A
>3.10. <A
HREF="reporting.html"
>Reports</A
></DT
></DL
></DIV
><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"
......@@ -262,7 +250,7 @@ WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="myaccount.html"
HREF="using-intro.html"
ACCESSKEY="N"
>Next</A
></TD
......@@ -282,7 +270,7 @@ VALIGN="top"
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>Create a Bugzilla Account</TD
>Introduction</TD
></TR
></TABLE
></DIV
......
docs/html/why-bugzilla.html
View file @ 96a0037a
......@@ -79,7 +79,8 @@ NAME="why-bugzilla"
></A
>2.3. Why use Bugzilla?</H1
><P
>Bugzilla boasts many advanced features. These include:
>Bugzilla is the leading open-source/free software bug tracking
system. It boasts many advanced features, including:
<P
></P
><UL
......@@ -117,12 +118,12 @@ NAME="why-bugzilla"
></LI
><LI
><P
>Web, XML, email and console interfaces</P
>Completely customisable and/or localisable web user
interface</P
></LI
><LI
><P
>Completely customisable and/or localisable web user
interface</P
>Additional XML, email and console interfaces</P
></LI
><LI
><P
......@@ -157,8 +158,7 @@ HREF="http://www.perforce.com"
TARGET="_top"
>Perforce SCM</A
>, Bugzilla
provides a powerful, easy-to-use solution to configuration management and
replication problems.</P
provides a powerful, easy-to-use configuration management solution.</P
></DIV
><DIV
CLASS="NAVFOOTER"
......
docs/html/why-tracking.html
View file @ 96a0037a
......@@ -79,23 +79,15 @@ NAME="why-tracking"
></A
>2.2. Why use a bug-tracking system?</H1
><P
>For many years, defect-tracking software was principally
the domain of large software development houses. Most smaller shops
simply relied on
shared lists and email to monitor the status of defects. This procedure
was error-prone and tended to cause those bugs judged least significant by
developers to be dropped or ignored.</P
>Those who do not use a bug-tracking system tend to rely on
shared lists, email, spreadsheets and/or Post-It notes to monitor the
status of defects. This procedure
is usually error-prone and tends to cause those bugs judged least
significant by developers to be dropped or ignored.</P
><P
>Integrated
defect-tracking systems reduce downtime, increase productivity, and raise
customer satisfaction with their systems. Along with full disclosure, an
open bug-tracker allows you to keep in touch with your clients
and resellers, to communicate about problems effectively throughout the
data management chain. Many corporations have also discovered that
defect-tracking helps reduce costs by providing IT support
accountability, telephone support knowledge bases, and a common,
well-understood method for accounting for unusual system or software
issues.</P
>Integrated defect-tracking systems make sure that nothing gets
swept under the carpet; they provide a method of creating, storing,
arranging and processing defect reports and enhancement requests.</P
></DIV
><DIV
CLASS="NAVFOOTER"
......
docs/pdf/Bugzilla-Guide.pdf
View file @ 96a0037a
This source diff could not be displayed because it is too large. You can view the blob instead.
docs/xml/Bugzilla-Guide.xml
View file @ 96a0037a
......@@ -40,11 +40,11 @@
<!ENTITY bz "http://www.bugzilla.org/">
<!ENTITY bzg-bugs "<ulink url='http://bugzilla.mozilla.org/enter_bug.cgi?product=Bugzilla&amp;component=Documentation'>Bugzilla Documentation</ulink>">
<!ENTITY mysql "http://www.mysql.com/">
<!ENTITY newest-perl-ver "5.8">
<!ENTITY newest-perl-ver "5.8.2">
<!-- For minimum versions -->
<!ENTITY min-mysql-ver "3.23.41">
<!ENTITY min-perl-ver "5.6">
<!ENTITY min-perl-ver "5.6.0">
<!ENTITY min-template-ver "2.08">
<!ENTITY min-file-temp-ver "any">
<!ENTITY min-appconfig-ver "1.52">
......
docs/xml/about.xml
View file @ 96a0037a
......@@ -67,17 +67,15 @@
]]>
</para>
<para>
The newest version of this guide can always be found at <ulink
url="http://www.bugzilla.org"/>; however, you should read the version
The latest version of this guide can always be found at <ulink
url="http://www.bugzilla.org"/>, or checked out via CVS.
(Please follow the <ulink url="http://www.mozilla.org/cvs.html">Mozilla
CVS</ulink> instructions and check out the
<filename>mozilla/webtools/bugzilla/docs/</filename>
subtree.) However, you should read the version
which came with the Bugzilla release you are using.
</para>
<para>
The latest version of this document can always be checked out via CVS.
Please follow the <ulink url="http://www.mozilla.org/cvs.html">Mozilla CVS</ulink>
instructions and check out the <filename>mozilla/webtools/bugzilla/docs/</filename>
subtree.
</para>
<para>
The Bugzilla Guide is currently only available in English.
If you would like to volunteer to translate it, please contact
<ulink url="mailto:justdave@syndicomm.com">Dave Miller</ulink>.
......@@ -116,7 +114,7 @@
<para>
Last but not least, all the members of the
<ulink url="news://news.mozilla.org/netscape/public/mozilla/webtools">
<ulink url="news://news.mozilla.org/netscape.public.mozilla.webtools">
netscape.public.mozilla.webtools</ulink>
newsgroup. Without your discussions, insight, suggestions, and patches,
this could never have happened.
......
docs/xml/conventions.xml
View file @ 96a0037a
......@@ -20,7 +20,7 @@
<tbody>
<row>
<entry>Warnings</entry>
<entry>Warning</entry>
<entry>
<caution>
......@@ -40,7 +40,7 @@
</row>
<row>
<entry>Notes</entry>
<entry>Note</entry>
<entry>
<note>
......@@ -60,7 +60,7 @@
</row>
<row>
<entry>File and directory names</entry>
<entry>File or directory name</entry>
<entry>
<filename>filename</filename>
......@@ -68,7 +68,7 @@
</row>
<row>
<entry>Commands to be typed</entry>
<entry>Command to be typed</entry>
<entry>
<command>command</command>
......@@ -76,7 +76,7 @@
</row>
<row>
<entry>Applications names</entry>
<entry>Application name</entry>
<entry>
<application>application</application>
......@@ -85,27 +85,21 @@
<row>
<entry>
<foreignphrase>Prompt</foreignphrase>
of users command under bash shell</entry>
Normal user's prompt under bash shell</entry>
<entry>bash$</entry>
</row>
<row>
<entry>
<foreignphrase>Prompt</foreignphrase>
of root users command under bash shell</entry>
Root user's prompt under bash shell</entry>
<entry>bash#</entry>
</row>
<row>
<entry>
<foreignphrase>Prompt</foreignphrase>
of user command under tcsh shell</entry>
Normal user's prompt under tcsh shell</entry>
<entry>tcsh$</entry>
</row>
......
docs/xml/introduction.xml
View file @ 96a0037a
......@@ -17,30 +17,23 @@
<section id="why-tracking">
<title>Why use a bug-tracking system?</title>
<para>For many years, defect-tracking software was principally
the domain of large software development houses. Most smaller shops
simply relied on
shared lists and email to monitor the status of defects. This procedure
was error-prone and tended to cause those bugs judged least significant by
developers to be dropped or ignored.</para>
<para>Integrated
defect-tracking systems reduce downtime, increase productivity, and raise
customer satisfaction with their systems. Along with full disclosure, an
open bug-tracker allows you to keep in touch with your clients
and resellers, to communicate about problems effectively throughout the
data management chain. Many corporations have also discovered that
defect-tracking helps reduce costs by providing IT support
accountability, telephone support knowledge bases, and a common,
well-understood method for accounting for unusual system or software
issues.</para>
<para>Those who do not use a bug-tracking system tend to rely on
shared lists, email, spreadsheets and/or Post-It notes to monitor the
status of defects. This procedure
is usually error-prone and tends to cause those bugs judged least
significant by developers to be dropped or ignored.</para>
<para>Integrated defect-tracking systems make sure that nothing gets
swept under the carpet; they provide a method of creating, storing,
arranging and processing defect reports and enhancement requests.</para>
</section>
<section id="why-bugzilla">
<title>Why use Bugzilla?</title>
<para>Bugzilla boasts many advanced features. These include:
<para>Bugzilla is the leading open-source/free software bug tracking
system. It boasts many advanced features, including:
<itemizedlist>
<listitem>
<para>Powerful searching</para>
......@@ -75,12 +68,12 @@
</listitem>
<listitem>
<para>Web, XML, email and console interfaces</para>
<para>Completely customisable and/or localisable web user
interface</para>
</listitem>
<listitem>
<para>Completely customisable and/or localisable web user
interface</para>
<para>Additional XML, email and console interfaces</para>
</listitem>
<listitem>
......@@ -102,8 +95,7 @@
<ulink url="http://www.cvshome.org">CVS</ulink>,
<ulink url="http://www.mozilla.org/bonsai.html">Bonsai</ulink>, or
<ulink url="http://www.perforce.com">Perforce SCM</ulink>, Bugzilla
provides a powerful, easy-to-use solution to configuration management and
replication problems.</para>
provides a powerful, easy-to-use configuration management solution.</para>
</section>
</chapter>
......
docs/xml/using.xml
View file @ 96a0037a
......@@ -3,14 +3,17 @@
<chapter id="using">
<title>Using Bugzilla</title>
<para>This section contains information for end-users of Bugzilla.
There is a Bugzilla test installation, called
<ulink url="http://landfill.bugzilla.org/bugzilla-tip/">Landfill</ulink>,
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.</para>
<section id="using-intro">
<title>Introduction</title>
<para>This section contains information for end-users of Bugzilla.
There is a Bugzilla test installation, called
<ulink url="http://landfill.bugzilla.org/bugzilla-tip/">Landfill</ulink>,
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.</para>
</section>
<section id="myaccount">
<title>Create a Bugzilla Account</title>
......@@ -296,6 +299,12 @@
of each bug.</member>
<member>
<emphasis>CSV:</emphasis>
get the buglist as comma-separated values, for import into e.g.
a spreadsheet.</member>
<member>
<emphasis>Change Columns:</emphasis>
change the bug attributes which appear in the list.</member>
......@@ -313,11 +322,18 @@
Sends mail to the owners of all bugs on the list.</member>
<member>
<emphasis>Edit this query:</emphasis>
<emphasis>Edit Search:</emphasis>
If you didn't get exactly the results you were looking for, you can
return to the Query page through this link and make small revisions
to the query you just made so you get more accurate results.</member>
<member>
<emphasis>Remember Search As:</emphasis>
You can give a search a name and remember it; a link will appear
in your page footer giving you quick access to run it again later.
</member>
</simplelist>
</para>
</section>
......@@ -365,6 +381,24 @@
<para>Select "Commit" and send in your bug report.</para>
</listitem>
</orderedlist>
<para>Try to make sure that everything said in the summary is also
said in the first comment. Summaries are often updated and this will
ensure your original information is easily accessible.
</para>
<para>
You do not need to put "any" or similar strings in the URL field.
If there is no specific URL associated with the bug, leave this
field blank.
</para>
<para>If you feel a bug you filed was incorrectly marked as a
DUPLICATE of another, please question it in your bug, not
the bug it was duped to. Feel free to CC the person who duped it
if they are not already CCed.
</para>
</section>
<section id="patchviewer">
......@@ -552,27 +586,6 @@
out of the bug.
</para>
</section>
<section>
<title>Filing Bugs</title>
<para>Try to make sure that everything said in the summary is also
said in the first comment. Summaries are often updated and this will
ensure your original information is easily accessible.
</para>
<para>
You do not need to put "any" or similar strings in the URL field.
If there is no specific URL associated with the bug, leave this
field blank.
</para>
<para>If you feel a bug you filed was incorrectly marked as a
DUPLICATE of another, please question it in your bug, not
the bug it was duped to. Feel free to CC the person who duped it
if they are not already CCed.
</para>
</section>
</section>
<section id="userpreferences">
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment