prepare 2.10.0

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

diff --git a/developers-reference.sgml b/developers-reference.sgml
index 72e4c3a1aa8083097e3289d4569e275ffcb79563..7ffd5c16c05f8d8e0e29f6ff3e74aed266afbacf 100644 (file)
--- a/developers-reference.sgml
+++ b/developers-reference.sgml
@@ -5,7 +5,7 @@
   <!-- common, language independant entities -->
   <!entity % commondata  SYSTEM "common.ent" > %commondata;
   <!-- CVS revision of this document -->
-  <!entity cvs-rev "$Revision: 1.79 $">
+  <!entity cvs-rev "$Revision: 1.80 $">
 
   <!-- if you are translating this document, please notate the RCS
        revision of the developers reference here -->
@@ -185,7 +185,7 @@ or high-powered spy techniques.  See <ref id="key-maint"> for more
 information on maintaining your public key.
        <p>
 Debian uses the <prgn>GNU Privacy Guard</prgn> (package
-<package>gnupg</package> version 1 or better as its baseline standard.
+<package>gnupg</package> version 1 or better) as its baseline standard.
 You can use some other implementation of OpenPGP as well.  Note that
 OpenPGP is a open standard based on <url id="&url-rfc2440;" name="RFC
 2440">.
@@ -1932,14 +1932,14 @@ Maintainers interact with the BTS via email addresses at
 <tt>bugs.debian.org</tt>.  Documentation on available commands can be
 found at <url id="&url-bts;">, or, if you have installed the
 <package>doc-debian</package> package, you can look at the local files
-<file>/usr/doc/debian/bug-*</file>.
+&file-bts-docs;.
        <p>
 Some find it useful to get periodic reports on open bugs.  You can add
 a cron job such as the following if you want to get a weekly email
 outlining all the open bugs against your packages:
 <example>
 # ask for weekly reports of bugs in my packages
-0 17 * * fri   echo "index maint <var>maintainer-address</var>" | mail request@bugs.debian.org
+&cron-bug-report;
 </example>
 Replace <var>maintainer-address</var> with you official Debian
 maintainer address.