diff options
| author | Xi Ruoyao <xry111@xry111.site> | 2023-07-27 10:03:30 +0800 |
|---|---|---|
| committer | Xi Ruoyao <xry111@xry111.site> | 2023-07-27 10:04:38 +0800 |
| commit | 49d402ee78cc17fab3501b544a83dca826f7a91d (patch) | |
| tree | 95c8e9da3d72fca2391bd9c461a90c9884dc4254 /chapter01/askforhelp.xml | |
| parent | b15bebf96f9df4260904cb682c1692bcc43891c2 (diff) | |
askforhelp: Reword the note added in previous commit a little
Diffstat (limited to 'chapter01/askforhelp.xml')
| -rw-r--r-- | chapter01/askforhelp.xml | 9 |
1 files changed, 5 insertions, 4 deletions
diff --git a/chapter01/askforhelp.xml b/chapter01/askforhelp.xml index 405b40804..5eb1d939f 100644 --- a/chapter01/askforhelp.xml +++ b/chapter01/askforhelp.xml @@ -12,10 +12,11 @@ <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 + In case you've hit an issue building one package with the LFS + instruction, we strongly discourage posting the issue directly onto + the upstream support channel before discussing via a LFS support + channel listed in <xref linkend="ch-intro-resources"/>. + 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 |