NMUs: Talk about sending the nmudiff as part of the NMU, rather than in advance.

diff --git a/debian/changelog b/debian/changelog
index 4c38da2ed5a2536ecb10ba015ae3bb6c261628a2..61f04765fc0e16c48f947c996325a91f8abbf328 100644 (file)
--- a/debian/changelog
+++ b/debian/changelog
@@ -17,6 +17,8 @@ developers-reference (3.4.14~~iwj) UNRELEASED; urgency=low
   * NMUs: Talk about `the maintainer [having] an opportunity to comment'
     rather than suggesting specifically that the NMUer should contact the
     maintainer.  Also slightly improve the wording of that paragraph.
+  * NMUs: Talk about sending the nmudiff as part of the NMU, rather
+    than in advance.
 
  --
 

diff --git a/pkgs.dbk b/pkgs.dbk
index 93c3b240619c9941c60088010325a0fc754c5b61..d57e4dd726ff23d0f50e5fdc198d5a92aa5d1a77 100644 (file)
--- a/pkgs.dbk
+++ b/pkgs.dbk
@@ -2023,9 +2023,8 @@ opportunity to upload a fix on their own.
 </listitem>
 </itemizedlist>
 <para>
-When doing an NMU, you must first make sure that your intention to NMU is
-clear.  Then, you must send a patch with the differences between the
-current package and your proposed NMU to the BTS. The
+When doing an NMU, you must send a patch with the differences between the
+current package and your NMU to the BTS. The
 <command>nmudiff</command> script in the <systemitem role="package">devscripts</systemitem> package
 might be helpful.
 </para>