Small simplification.

[bugscan.git] / dohtml

diff --git a/dohtml b/dohtml
index e06f9bb609fd473525c3fe29fe8d97bb01beb8f3..1e9a6ab6dbd7f644cfba7ad804ecb352d78be5ae 100755 (executable)
--- a/dohtml
+++ b/dohtml
@@ -39,17 +39,6 @@ EOF
        ./bugreport -H -s $filter
        
        cat <<EOF
-<p>
-Explanation for comment tags:
-<ul>
-   <li><strong>[FIX]</strong>: describes a simple method to deal with
-       the bug.
-   <li><strong>[STRATEGY]</strong>: describes a possible approach for
-       fixing the bug.
-   <li><strong>[HELP]</strong>: help is needed to fix this bug.
-   <li><strong>[REMOVE]</strong>: package will be removed if bug is not fixed
-</ul>
-
 <p>
 Explanation for <a href="http://www.debian.org/Bugs/Developer#tags">bug
 tags</a>:
@@ -66,10 +55,9 @@ tags</a>:
 </ul>
 
 <p>
-Some bugs have an additional set of tags indicating they only apply
-to a particular release: O for oldstable (woody), S for stable (sarge),
-T for testing (etch), U for unstable (sid) or E for experimental. X
-indicates that the package is not in testing.
+The second set of tags indicate what releases a bug applies to:
+O for oldstable (woody), S for stable (sarge), T for testing (etch),
+U for unstable (sid) or E for experimental.
 
 <p>
 
@@ -113,7 +101,8 @@ EOF
 line graphs the number of bugs that are actually a concern for the next
 release (excluding ignored bugs, bugs on packages not in testing, and bugs
 whose tags and/or versioning information indicate that they don't apply to
-testing).</p>
+testing), and the blue line graphs the number of bugs that are a concern
+for the <em>current</em> stable release.</p>
 
 <h2>Recent changes</h2>
 EOF