Author: stef-guest
Date: 2006-05-20 13:18:27 +0000 (Sat, 20 May 2006)
New Revision: 4001
Modified:
doc/narrative_introduction
Log:
add "bug filed" to narrative introduction
Modified: doc/narrative_introduction
===================================================================
--- doc/narrative_introduction 2006-05-20 13:17:58 UTC (rev 4000)
+++ doc/narrative_introduction 2006-05-20 13:18:27 UTC (rev 4001)
@@ -171,12 +171,14 @@
- php4 <unfixed> (bug #353585; medium)
- php5 <unfixed> (bug #353585; medium)
-Bug numbers can be added as in the example above. They are used to add
-additional references for the overview page and the Security Bug Tracker
-and they are parsed by a script that generates user tags "tracked" for the
-user [EMAIL PROTECTED] This way you can generate a BTS
-query for all issues in the BTS that are tagged "security" and are not
-yet added to our tracker:
+Bug numbers can be added as in the example above. To avoid duplicate bugs,
+"bug filed" can be added instead of "bug #123456" when the bug report has
+been sent but the bug number is not yet known. The bug numbers are used
+to add additional references for the overview page and the Security Bug
+Tracker and they are parsed by a script that generates user tags "tracked"
+for the user [EMAIL PROTECTED] This way you can generate
+a BTS query for all issues in the BTS that are tagged "security" and are
+not yet added to our tracker:
http://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=security;[EMAIL
PROTECTED];exclude=tracked
If a vulnerability does not affect Debian, e.g. because the vulnerable
_______________________________________________
Secure-testing-commits mailing list
Secure-testing-commits@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/secure-testing-commits
