small enhancements

git-svn-id: svn://anonscm.debian.org/ddp/manuals/trunk/developers-reference@2609 313b444b-1b9f-4f58-a734-7bb04f332e8d

diff --git a/developers-reference.sgml b/developers-reference.sgml
index 0756207a555a8ac381af2e21c7860d40194b766b..df9990b2122b30dc8fcc6b31831b2a1286963bee 100644 (file)
--- 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.241 $">
+  <!ENTITY cvs-rev "$Revision: 1.242 $">
 
   <!-- if you are translating this document, please notate the CVS
        revision of the original developer's reference in cvs-en-rev -->
@@ -2006,9 +2006,8 @@ doing so, please read the <url id="&url-tech-ctte;" name="recommended procedure"
     <item>
 If the bug is real but it's caused by another package, just reassign
 the bug to the right package. If you don't know which package it should
-be reassigned to, you may either ask for help on &email-debian-devel; or
-reassign it to <package>debian-policy</package> to let them decide which
-package is at fault.
+be reassigned to, you should ask for help on
+<ref id="irc-channels" name="IRC"> or on &email-debian-devel;.
     <p>
 Sometimes you also have to adjust the severity of the bug so that it
 matches our definition of the severity. That's because people tend to
@@ -2801,7 +2800,7 @@ Under certain circumstances it is necessary for someone other than the
 official package maintainer to make a release of a package. This is
 called a non-maintainer upload, or NMU.
        <p>
-This sections handles only source NMUs, i.e. NMUs which upload a new
+This section handles only source NMUs, i.e. NMUs which upload a new
 version of the package. For binary-only NMUs by porters or QA members,
 please see <ref id="binary-only-nmu">.
 For buildd uploads (which are strictly speaking also NMUs), please see <ref
@@ -3009,8 +3008,11 @@ changes file.
 If one of your packages has been NMU'ed, you have to incorporate the
 changes in your copy of the sources. This is easy, you just have
 to apply the patch that has been sent to you. Once this is done, you
-have to close the bugs that have been tagged fixed by the NMU. You
-can either close them manually by sending the required mails to the
+have to close the bugs that have been tagged fixed by the NMU. The easiest
+way is to use the <tt>-v</tt> option of <prgn>dpkg-buildpackage</prgn>,
+as this allows you to include just all changes since your last maintainer
+upload. Alternativly, you
+can close them manually by sending the required mails to the
 BTS or by adding the required <tt>closes: #nnnn</tt> in the changelog
 entry of your next upload.
        <p>