remove spurious CDATA notation

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

diff --git a/developers-reference.sgml b/developers-reference.sgml
index a86386ec698e921b12591d62fe783296e22639e7..8b59385eb5fa70944b117dccb42a124fa961c50e 100644 (file)
--- a/developers-reference.sgml
+++ b/developers-reference.sgml
@@ -1,20 +1,20 @@
 <!DOCTYPE debiandoc PUBLIC "-//DebianDoc//DTD DebianDoc//EN" [
   <!-- include version information so we don't have to hard code it
        within the document -->
-  <!entity % versiondata SYSTEM "version.ent"> %versiondata;
+  <!ENTITY % versiondata SYSTEM "version.ent"> %versiondata;
   <!-- common, language independant entities -->
-  <!entity % commondata  SYSTEM "common.ent" > %commondata;
+  <!ENTITY % commondata  SYSTEM "common.ent" > %commondata;
 
   <!-- CVS revision of this document -->
-  <!entity cvs-rev "$Revision: 1.205 $">
+  <!ENTITY cvs-rev "$Revision: 1.208 $">
   <!-- if you are translating this document, please notate the CVS
        revision of the developers reference here -->
   <!--
-    <!entity cvs-en-rev "X.YY">
+  <!ENTITY cvs-en-rev "X.YY">
     -->
 
-  <!--  -->
-  <!entity FIXME "<em>FIXME:</em>&nbsp;">
+  <!-- how to mark a section that needs more work -->
+  <!ENTITY FIXME "<em>FIXME:</em>&nbsp;">
 
 ]>
 <debiandoc>
@@ -1735,6 +1735,10 @@ to transfer the files, place them into &us-upload-dir;;
 if you use anonymous FTP to upload, place them into
 &upload-queue;.
          <p>
+If you want to use feature described in <ref id="delayed-incoming">,
+you'll have to upload to <tt>ftp-master</tt>.  It is the only upload
+point that supported delayed incoming.
+         <p>
 Please note that you should transfer
 the changes file last.  Otherwise, your upload may be rejected because the
 archive maintenance software will parse the changes file and see that not
@@ -1974,7 +1978,8 @@ maintainer address.
 
       <sect1 id="bug-answering">Responding to bugs
        <p>
-Make sure that any discussion you have about bugs are sent both to
+When responding to bugs, make sure that any discussion you have about
+bugs are sent both to
 the original submitter of the bug, and the bug itself (e.g.,
 <email>123@&bugs-host;</email>). If you're writing a new
 mail and you don't remember the submitter email address, you can
@@ -1983,6 +1988,9 @@ contact the submitter <em>and</em> to record your mail within the
 bug log (that means you don't need to send a copy of the mail to
 <email>123@&bugs-host;</email>).
        <p>
+If you get a bug which mentions "FTBFS", that means "Fails to build
+from source".  Porters frequently use this acronym.
+       <p>
 Once you've dealt with a bug report (e.g. fixed it), mark it as
 <em>done</em> (close it) by sending an explanation message to
 <email>123-done@&bugs-host;</email>. If you're fixing a bug by