Changeset b15bebf for chapter01

Timestamp:

07/27/2023 01:43:57 AM (10 months ago)

Author:

Xi Ruoyao <xry111@…>

Branches:

12.0, 12.0-rc1, 12.1, 12.1-rc1, multilib, trunk, xry111/arm64, xry111/arm64-12.0, xry111/clfs-ng, xry111/loongarch, xry111/loongarch-12.0, xry111/loongarch-12.1, xry111/mips64el, xry111/update-glibc

Children:

49d402e

Parents:

fb3b88e

git-author:

Xi Ruoyao <xry111@…> (07/27/2023 01:43:35 AM)

git-committer:

Xi Ruoyao <xry111@…> (07/27/2023 01:43:57 AM)

Message:

askforhelp: Add a note to stop people from spamming upstream

I've seen two cases of invalid upstream "bug" reports this month because
the user has (mis)built LFS. Let's stop this before irritating the
upstream maintainers.

File:

• chapter01/askforhelp.xml (modified) (1 diff)

chapter01/askforhelp.xml

@@ -10 +10 @@
 
   <title>Help</title>
+
+  <note>
+    <para>
+      We strongly discourage posting your issues building one LFS package
+      directly onto the upstream support channel, without discussing via
+      a LFS support channel listed in <xref linkend="ch-intro-resources"/>
+      first.  Doing so is often quite inefficient because the upstream
+      maintainers are rarely familiar with LFS building procedure.  Even if
+      you've really hit an upstream issue, the LFS community can still help
+      to isolate the information wanted by the upstream maintainers and make
+      a proper report.
+    </para>
+
+    <para>
+      If you must ask a question directly via an upstream support channel,
+      you shall at least note that many upstream projects have the support
+      channels separated from the bug tracker.  The <quote>bug</quote>
+      reports for asking questions are considered invalid and may annoy
+      upstream developers for these projects.
+    </para>
+  </note>
 
   <para>If an issue or a question is encountered while working through