Don't claim that -arch is a moderated list. Also be more consistent

in the formatting of the list charters.
This commit is contained in:
Dima Dorfman 2001-04-12 01:49:55 +00:00
parent e8eb3912f3
commit 4a85daf2d4
Notes: svn2git 2020-12-08 03:00:23 +00:00
svn path=/head/; revision=9175
2 changed files with 36 additions and 42 deletions

View file

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/eresources/chapter.sgml,v 1.54 2001/04/01 01:17:24 dd Exp $
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/eresources/chapter.sgml,v 1.55 2001/04/09 00:33:50 dd Exp $
-->
<appendix id="eresources">
@ -612,11 +612,10 @@ help
<para><emphasis>Architecture and design
discussions</emphasis></para>
<para>This is a moderated list for discussion of FreeBSD
architecture. Messages will mostly be kept technical in nature,
with (rare) exceptions for other messages the moderator deems
need to reach all the subscribers of the list. Examples of
suitable topics;</para>
<para>This list is for discussion of the FreeBSD
architecture. Messages will mostly be kept strictly
technical in nature. Examples of suitable topics
are:</para>
<itemizedlist>
<listitem>
@ -631,20 +630,14 @@ help
<listitem>
<para>How do we change the device driver interface to be able
to use the ame drivers cleanly on many buses and
architectures?</para>
to use the same drivers cleanly on many buses and
architectures.</para>
</listitem>
<listitem>
<para>How do I write a network driver?</para>
<para>How to write a network driver.</para>
</listitem>
</itemizedlist>
<para>The moderator reserves the right to do minor editing
(spell-checking, grammar correction, trimming) of messages that
are posted to the list. The volume of the list will be kept
low, which may involve having to delay topics until an active
discussion has been resolved.</para>
</listitem>
</varlistentry>
@ -756,7 +749,7 @@ help
<term>FREEBSD-IPFW</term>
<listitem>
<para>IP Firewall</para>
<para><emphasis>IP Firewall</emphasis></para>
<para>This is the forum for technical discussions concerning the
redesign of the IP firewall code in FreeBSD. This is a
@ -917,7 +910,7 @@ help
<term>FREEBSD-POLICY</term>
<listitem>
<para>Core team policy decisions</para>
<para><emphasis>Core team policy decisions</emphasis></para>
<para>This is a low volume, read-only mailing list for FreeBSD
Core Team Policy decisions.</para>
@ -993,10 +986,11 @@ help
<term>FREEBSD-SECURITY-NOTIFICATIONS</term>
<listitem>
<para><emphasis>Security Notifications</emphasis>
Notifications of FreeBSD security problems and fixes. This is
not a discussion list. The discussion list is
FreeBSD-security.</para>
<para><emphasis>Security Notifications</emphasis></para>
<para>Notifications of FreeBSD security problems and
fixes. This is not a discussion list. The discussion
list is FreeBSD-security.</para>
</listitem>
</varlistentry>
@ -1004,6 +998,9 @@ help
<term>FREEBSD-SMALL</term>
<listitem>
<para><emphasis>Using FreeBSD in embedded
applications</emphasis></para>
<para>This list discusses topics related to unusually small and
embedded FreeBSD installations. This is a technical mailing
list for which strictly technical content is expected.</para>

View file

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/eresources/chapter.sgml,v 1.54 2001/04/01 01:17:24 dd Exp $
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/eresources/chapter.sgml,v 1.55 2001/04/09 00:33:50 dd Exp $
-->
<appendix id="eresources">
@ -612,11 +612,10 @@ help
<para><emphasis>Architecture and design
discussions</emphasis></para>
<para>This is a moderated list for discussion of FreeBSD
architecture. Messages will mostly be kept technical in nature,
with (rare) exceptions for other messages the moderator deems
need to reach all the subscribers of the list. Examples of
suitable topics;</para>
<para>This list is for discussion of the FreeBSD
architecture. Messages will mostly be kept strictly
technical in nature. Examples of suitable topics
are:</para>
<itemizedlist>
<listitem>
@ -631,20 +630,14 @@ help
<listitem>
<para>How do we change the device driver interface to be able
to use the ame drivers cleanly on many buses and
architectures?</para>
to use the same drivers cleanly on many buses and
architectures.</para>
</listitem>
<listitem>
<para>How do I write a network driver?</para>
<para>How to write a network driver.</para>
</listitem>
</itemizedlist>
<para>The moderator reserves the right to do minor editing
(spell-checking, grammar correction, trimming) of messages that
are posted to the list. The volume of the list will be kept
low, which may involve having to delay topics until an active
discussion has been resolved.</para>
</listitem>
</varlistentry>
@ -756,7 +749,7 @@ help
<term>FREEBSD-IPFW</term>
<listitem>
<para>IP Firewall</para>
<para><emphasis>IP Firewall</emphasis></para>
<para>This is the forum for technical discussions concerning the
redesign of the IP firewall code in FreeBSD. This is a
@ -917,7 +910,7 @@ help
<term>FREEBSD-POLICY</term>
<listitem>
<para>Core team policy decisions</para>
<para><emphasis>Core team policy decisions</emphasis></para>
<para>This is a low volume, read-only mailing list for FreeBSD
Core Team Policy decisions.</para>
@ -993,10 +986,11 @@ help
<term>FREEBSD-SECURITY-NOTIFICATIONS</term>
<listitem>
<para><emphasis>Security Notifications</emphasis>
Notifications of FreeBSD security problems and fixes. This is
not a discussion list. The discussion list is
FreeBSD-security.</para>
<para><emphasis>Security Notifications</emphasis></para>
<para>Notifications of FreeBSD security problems and
fixes. This is not a discussion list. The discussion
list is FreeBSD-security.</para>
</listitem>
</varlistentry>
@ -1004,6 +998,9 @@ help
<term>FREEBSD-SMALL</term>
<listitem>
<para><emphasis>Using FreeBSD in embedded
applications</emphasis></para>
<para>This list discusses topics related to unusually small and
embedded FreeBSD installations. This is a technical mailing
list for which strictly technical content is expected.</para>