From: aph Date: Mon, 16 Nov 1998 05:39:43 +0000 (+0000) Subject: name change X-Git-Url: http://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?a=commitdiff_plain;h=3e556c53557693ba3f22617458681e073775a78c;p=developers-reference.git name change fix SGML nit git-svn-id: svn://anonscm.debian.org/ddp/manuals/trunk/developers-reference@721 313b444b-1b9f-4f58-a734-7bb04f332e8d --- diff --git a/developers-reference.sgml b/developers-reference.sgml index dc63811..87d1cfe 100644 --- a/developers-reference.sgml +++ b/developers-reference.sgml @@ -8,20 +8,22 @@ TODO: - bugs in upstream versions should be reported upstream! - add information on how to get accounts on different architectures - - talk about CVS access + - talk about CVS access, other ways to submit problems + - add information on how you can contribute w/o being an official + developer --> Debian Developer's Reference - <author>Adam P. Harris, current maintainer <email/aph@debian.org/ + <author>Adam Di Carlo, current maintainer <email/aph@debian.org/ <author>Christian Schwarz <email/schwarz@debian.org/ <author>Ian Jackson <email/ijackson@gnu.ai.mit.edu/ <version>ver. &version;, &date; <copyright> <copyrightsummary><!-- this tag not working right --> -copyright ©1998 Adam P. Harris, ©1997,1998 +copyright ©1998 Adam Di Carlo, ©1997,1998 Christian Schwarz</copyrightsummary> <p> This manual is free software; you may redistribute it and/or modify it @@ -1038,7 +1040,7 @@ how NMUs should be done. <p> Only an official Debian developers can do an NMU. <!-- TODO: link to section talking about how non-maintainers can still -contribute --> + contribute --> <sect id="nmu-when">When to do an NMU <p> @@ -1146,7 +1148,7 @@ you'll have to invoke <prgn>dpkg-buildpackage</prgn> with the <tt/-sa/ switch to force the build system to pick up the new source package (normally it only looks for Debian revisions of '0' or '1'). <p> -<!--- HERE ---> +<!-- HERE --> Maintainers other than the usual package maintainer should make as few changes to the package as possible, and they should always send a unified context diff (<tt/diff -u/) detailing their changes to the bug