From: aph <aph@313b444b-1b9f-4f58-a734-7bb04f332e8d>
Date: Mon, 16 Jun 2003 08:03:41 +0000 (+0000)
Subject: Sec "Responding to bugs": mention what FTBFS means; closes: #186605
X-Git-Url: http://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?a=commitdiff_plain;h=9f27e25e90940ec82d1995501e41d1636f102c96;p=developers-reference.git

Sec "Responding to bugs": mention what FTBFS means; closes: #186605


git-svn-id: svn://anonscm.debian.org/ddp/manuals/trunk/developers-reference@2332 313b444b-1b9f-4f58-a734-7bb04f332e8d
---

diff --git a/debian/changelog b/debian/changelog
index 3c52794..1145243 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -17,6 +17,7 @@ developers-reference (3.3.3) unstable; urgency=low
     - Sec "Managing sponsored packages": remove unnecessary 'debsign' cmd;
       closes: #192417
     - fix debconf-devel(7) man page section; closes: #189512
+    - Sec "Responding to bugs": mention what FTBFS means; closes: #186605
     - Sec "Distribution directories" renamed "Distributions"
     - Sec "The testing distribution" moved under Sec "Distribution
       directories" and renamed "More information about the testing
@@ -24,7 +25,7 @@ developers-reference (3.3.3) unstable; urgency=low
     - Secs "Uploads to {stable,testing-proposed-updates}" retitled to make
       it clear these are special cases
 
- -- Adam Di Carlo <aph@debian.org>  Mon, 16 Jun 2003 03:11:42 -0400
+ -- Adam Di Carlo <aph@debian.org>  Mon, 16 Jun 2003 03:59:01 -0400
 
 developers-reference (3.3.2) unstable; urgency=low
 
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