From e1c0827f89e5514b2310c6a2096e1c0bcc4cf145 Mon Sep 17 00:00:00 2001 From: aba Date: Sun, 12 Nov 2006 10:17:59 +0000 Subject: [PATCH] append NMU-diff to the bug git-svn-id: svn://anonscm.debian.org/ddp/manuals/trunk/developers-reference@3959 313b444b-1b9f-4f58-a734-7bb04f332e8d --- debian/changelog | 1 + developers-reference.sgml | 4 ++-- 2 files changed, 3 insertions(+), 2 deletions(-) diff --git a/debian/changelog b/debian/changelog index f4e3c84..bad7a81 100644 --- a/debian/changelog +++ b/debian/changelog @@ -34,6 +34,7 @@ developers-reference (3.3.8) unstable; urgency=low * Hint to dd-list/whodepends. Closes: #353874 * Don't use too generic mail ids. Closes: #355725 * pts/summary is actually used. Thanks, Holger Levsen. Closes: #387108 + * clarify that one should append the NMU-diff to a bug. Closes: #394033 -- Andreas Barth Sat, 11 Nov 2006 10:55:44 -0700 diff --git a/developers-reference.sgml b/developers-reference.sgml index 859de1d..9db7ba8 100644 --- a/developers-reference.sgml +++ b/developers-reference.sgml @@ -7,7 +7,7 @@ %dynamicdata; - + @@ -3192,7 +3192,7 @@ the official package maintainer. Also, after doing an NMU, you have to send the information to the existing bugs that are fixed by your NMU, including the unified diff. -Alternatively you can open a new bug and include a +Historically, it was custom to open a new bug and include a patch showing all the changes you have made. The normal maintainer will either apply the patch or employ an alternate method of fixing the problem. Sometimes bugs are fixed independently -- 2.30.2