[Secure-testing-commits] r12570 - doc
Michael Gilbert
gilbert-guest at alioth.debian.org
Tue Aug 11 20:38:42 UTC 2009
Author: gilbert-guest
Date: 2009-08-11 20:38:42 +0000 (Tue, 11 Aug 2009)
New Revision: 12570
Modified:
doc/narrative_introduction
Log:
removing duplicated user tags discussion (there is now a section devoted to it)
Modified: doc/narrative_introduction
===================================================================
--- doc/narrative_introduction 2009-08-11 20:00:38 UTC (rev 12569)
+++ doc/narrative_introduction 2009-08-11 20:38:42 UTC (rev 12570)
@@ -199,13 +199,7 @@
the entry in the CVE list so that complete information is always available
in the tracker). The bug number is important because it makes it clear
that the maintainer has been contacted about the problem, and that they are
-aware of their responsibility to work swiftly toward a fix. The bug
-numbers are also used to add additional references for the overview page
-and the Security Bug Tracker. They are parsed by a script that generates
-user tags "tracked" for the user debian-security at lists.debian.org, which
-enables BTS users to generate a query for all of the issues that are tagged
-"security" but not yet added to the tracker:
-http://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=security;users=debian-security@lists.debian.org;exclude=tracked
+aware of their responsibility to work swiftly toward a fix.
Since CVEs often drop in bulk, submission of multiple CVEs in a single bug
report is permissable and encouraged. However, some maintainers have
More information about the Secure-testing-commits
mailing list