From c841e855f96935e91d28e604e0811e1f6d76543d Mon Sep 17 00:00:00 2001
From: joy <joy@313b444b-1b9f-4f58-a734-7bb04f332e8d>
Date: Thu, 10 Oct 2002 21:09:20 +0000
Subject: [PATCH] the version of dpkg-dev that supports this feature is no
 longer new, so skip that; also rephrased the sentence better while i was at
 it

git-svn-id: svn://anonscm.debian.org/ddp/manuals/trunk/developers-reference@1848 313b444b-1b9f-4f58-a734-7bb04f332e8d
---
 developers-reference.sgml | 11 ++++++-----
 1 file changed, 6 insertions(+), 5 deletions(-)

diff --git a/developers-reference.sgml b/developers-reference.sgml
index a7251ba..e06eef8 100644
--- a/developers-reference.sgml
+++ b/developers-reference.sgml
@@ -6,7 +6,7 @@
   <!entity % commondata  SYSTEM "common.ent" > %commondata;
 
   <!-- CVS revision of this document -->
-  <!entity cvs-rev "$Revision: 1.135 $">
+  <!entity cvs-rev "$Revision: 1.136 $">
   <!-- if you are translating this document, please notate the CVS
        revision of the developers reference here -->
   <!--
@@ -2838,10 +2838,11 @@ been accepted into the Debian archive.  Therefore, once you get
 notification that your updated package has been installed into the
 archive, you can and should close the bug in the BTS.
 	<p>
-If you are using a new version of <package>dpkg-dev</package> and you do
-your changelog entry properly, the archive maintenance software will close
-the bugs automatically.  All you have to do is follow a certain syntax in
-your <file>debian/changelog</file> file:
+However, it's possible to avoid having to manually close bugs after the
+upload -- just list the fixed bugs in your <file>debian/changelog</file>
+file, following a certain syntax, and the archive maintenance software
+will close the bugs for you. For example:
+
 <example>
 acme-cannon (3.1415) unstable; urgency=low
 
-- 
2.30.2