From f22fac85d37bb53ff997ead5007ed40ed5cadf84 Mon Sep 17 00:00:00 2001 From: Ian Jackson Date: Sun, 31 Aug 2014 02:08:00 +0100 Subject: [PATCH] NMUs: Talk about sending the nmudiff as part of the NMU, rather than in advance. --- debian/changelog | 2 ++ pkgs.dbk | 5 ++--- 2 files changed, 4 insertions(+), 3 deletions(-) diff --git a/debian/changelog b/debian/changelog index 4c38da2..61f0476 100644 --- 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 93c3b24..d57e4dd 100644 --- a/pkgs.dbk +++ b/pkgs.dbk @@ -2023,9 +2023,8 @@ opportunity to upload a fix on their own. -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 nmudiff script in the devscripts package might be helpful. -- 2.30.2