X-Git-Url: http://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?a=blobdiff_plain;f=developers-reference.sgml;h=1585a4c568e4d12894b60b766d58f6c4b79adfe6;hb=9f27e25e90940ec82d1995501e41d1636f102c96;hp=a86386ec698e921b12591d62fe783296e22639e7;hpb=f6b74f287273767115c98b492382544bcf16776f;p=developers-reference.git

diff --git a/developers-reference.sgml b/developers-reference.sgml
index a86386e..1585a4c 100644
--- a/developers-reference.sgml
+++ b/developers-reference.sgml
@@ -6,7 +6,7 @@
   <!entity % commondata  SYSTEM "common.ent" > %commondata;
 
   <!-- CVS revision of this document -->
-  <!entity cvs-rev "$Revision: 1.205 $">
+  <!entity cvs-rev "$Revision: 1.206 $">
   <!-- if you are translating this document, please notate the CVS
        revision of the developers reference here -->
   <!--
@@ -1974,7 +1974,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 +1984,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