Changeset 4d19786
- Timestamp:
- 06/29/2023 06:19:19 AM (12 months ago)
- Branches:
- 12.0, 12.1, kea, ken/TL2024, ken/tuningfonts, lazarus, lxqt, plabs/newcss, python3.11, rahul/power-profiles-daemon, renodr/vulkan-addition, trunk, xry111/llvm18, xry111/xf86-video-removal
- Children:
- a1bb0d9
- Parents:
- 76f2fb4
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
introduction/welcome/wiki.xml
r76f2fb4 r4d19786 10 10 11 11 12 <title> BLFS Wiki</title>12 <title>Editor Notes</title> 13 13 14 <para>The BLFS Project has created a Wiki for users to comment on pages 15 and instructions at <ulink url='&blfs-wiki;'/>. 16 Comments are welcome from all users.</para> 14 <para>The BLFS Project has created a Wiki for editors to comment 15 on pages and instructions at <ulink url='&blfs-wiki;'/>.</para> 17 16 17 <para>When <emphasis>editor notes</emphasis> are present, a link 18 appears in the form <literal>&blfs-wiki;/pkgname</literal> right 19 below the dependency list. The idea behind the editor notes is to 20 give additional information about the package and/or its build 21 instructions, common pitfalls or maybe even more sophisticated 22 configuration for special cases of use.</para> 23 24 <para>The vast majority of the packages do not have editor notes.</para> 25 26 <note> 27 <para> 28 The <emphasis>editor notes</emphasis> might be outdated. Even 29 though the pages should be reviewed when a package is updated, 30 it might happen that there are notes referring to an obsolete 31 version and therefore, the notes might be out of date. Always 32 check the date of the notes and more importantly, the version 33 of the package the notes refer to. 34 </para> 35 </note> 36 37 <!-- 18 38 <para>The following are the rules for posting: 19 39 20 40 <itemizedlist> 21 41 <listitem> 22 <para>Users must register and log in to edit a page.</para> 42 <para>Due to excessive spamming, the commenting function is 43 restricted to authenticated users (editors) only.</para> 23 44 </listitem> 24 45 <listitem> … … 42 63 43 64 </para> 65 --> 44 66 45 67 </sect1>
Note:
See TracChangeset
for help on using the changeset viewer.