- Also mentions sending patchs in the BSP section.

[developers-reference.git] / developers-reference.sgml

diff --git a/developers-reference.sgml b/developers-reference.sgml
index 7bc7c88245ff24f30457cc2628df6bf658d4c899..22d739df3d06b48bdbdf05b3411c45e5c535e45f 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.129 $">
+  <!entity cvs-rev "$Revision: 1.130 $">
   <!-- if you are translating this document, please notate the CVS
        revision of the developers reference here -->
   <!--
@@ -3182,7 +3182,10 @@ NMU withour prior notice if they upload their NMU to
 DELAYED/3-day at least. All other NMU rules applies as usually, they
 should send the patch of the NMU in the BTS (in one of the open bugs
 fixed by the NMU or in a new bug tagged fixed). They should
-also respect the maintainer's wishes if he expressed some. 
+also respect the maintainer's wishes if he expressed some.
+       <p>
+If someone doesn't feel confident with an NMU, he should just send a patch
+to the BTS. It's far better than a broken NMU.
 
     <sect id="mia-qa">Dealing with unreachable maintainers
       <p>