From 2996dc36d2aaf2d329c2b5b1683108244863030d Mon Sep 17 00:00:00 2001 From: Michael Gilbert Date: Tue, 11 Aug 2009 20:38:42 +0000 Subject: removing duplicated user tags discussion (there is now a section devoted to it) git-svn-id: svn+ssh://svn.debian.org/svn/secure-testing@12570 e39458fd-73e7-0310-bf30-c45bca0a0e42 --- doc/narrative_introduction | 8 +------- 1 file changed, 1 insertion(+), 7 deletions(-) (limited to 'doc/narrative_introduction') diff --git a/doc/narrative_introduction b/doc/narrative_introduction index 93f14ba24c..f64098372c 100644 --- a/doc/narrative_introduction +++ b/doc/narrative_introduction @@ -199,13 +199,7 @@ desirable to file the bug, wait for the BTS to assign a number, then update 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@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 -- cgit v1.2.3