From 5d3976a50f596cde69715a7c14b093f8dfdae776 Mon Sep 17 00:00:00 2001
From: "bryce-mozilla%nextbus.com" <>
Date: Wed, 12 May 1999 11:40:02 +0000
Subject: I keep chipping away at the Mozilla-specific things.

---
 bug_status.html | 21 +--------------------
 1 file changed, 1 insertion(+), 20 deletions(-)

(limited to 'bug_status.html')

diff --git a/bug_status.html b/bug_status.html
index 9bb68272f..3fd38c60e 100755
--- a/bug_status.html
+++ b/bug_status.html
@@ -145,21 +145,6 @@ prioritized their work to be done.  The available priorities are:
 </table>
 </tr></table>
 
-
-<a name="area"><h2>Area</h2></a>
-This is the general area which is covered by the bug report.  This allows
-bugs to migrate over to testing, but not show up on the "daily bug list".
-Most bugs should have area set to <B>CODE</B>.  Legal values include:
-<UL>
-<LI> CODE
-<LI> JAVA
-<LI> TEST
-<LI> UI
-<LI> BUILD
-<LI> PERF
-<LI> i18n <i>(internationalization)</i>
-<LI> l10n <i>(localization)</i>
-</UL>
 <a name="rep_platform"><h2>Platform</h2></a>
 This is the hardware platform against which the bug was reported.  Legal
 platforms include:
@@ -195,10 +180,6 @@ This is the person in charge of resolving the bug.  Every time this
 field changes, the status changes to <B>NEW</B> to make it easy to see
 which new bugs have appeared on a person's list.
 
-<p><A HREF="http://www.mozilla.org/owners.html">List of module owners.</a>
-<p>
-
-
 The default status for queries is set to NEW, ASSIGNED and REOPENED. When
 searching for bugs that have been resolved or verified, remember to set the
 status field appropriately. 
@@ -206,6 +187,6 @@ status field appropriately.
 <hr>
 <address><a href="http://home.netscape.com/people/terry/">Terry Weissman &lt;terry@netscape.com&gt;</a></address>
 <!-- hhmts start -->
-Last modified: Fri Apr 30 13:14:35 1999
+Last modified: Tue May 11 21:34:56 1999
 <!-- hhmts end -->
 </body> </html>
-- 
cgit v1.2.3-24-g4f1b