Correct a bit of bogus information about core controlling mailing

list membership and reorder some of the lists into more appropriate
categories.
This commit is contained in:
Jordan K. Hubbard 1999-09-28 22:33:04 +00:00
parent cfbec7b7fc
commit d245ff4940
Notes: svn2git 2020-12-08 03:00:23 +00:00
svn path=/head/; revision=5760
2 changed files with 32 additions and 24 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.30 1999/09/14 03:17:46 jim Exp $
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/eresources/chapter.sgml,v 1.31 1999/09/15 21:55:22 kuriyama Exp $
-->
<chapter id="eresources">
@ -239,6 +239,11 @@
<entry>Security issues</entry>
</row>
<row>
<entry>freebsd-security-notifications</entry>
<entry>Security notifications</entry>
</row>
<row>
<entry>freebsd-small</entry>
<entry>Using FreeBSD in embedded applications</entry>
@ -263,12 +268,11 @@
</tgroup>
</informaltable>
<para><emphasis>Limited lists:</emphasis> The following lists require
approval from <email>core@FreeBSD.org</email> to join, though anyone
is free to send messages to them which fall within the scope of their
charters. It is also a good idea establish a presence in the
technical lists before asking to join one of these limited
lists.</para>
<para><emphasis>Limited lists:</emphasis> The following lists are for
more specialized (and demanding) audiences and are probably not of
interest to the general public. It is also a good idea to establish a
presence in the technical lists before joining one of these limited
lists so that you'll understand the communications etiquette involved.</para>
<informaltable frame="none">
<tgroup cols="2">
@ -306,15 +310,15 @@
<entry>Installation development</entry>
</row>
<row>
<entry>freebsd-security-notifications</entry>
<entry>Security notifications</entry>
</row>
<row>
<entry>freebsd-user-groups</entry>
<entry>User group coordination</entry>
</row>
<row>
<entry>freebsd-www</entry>
<entry>Maintainers of <ulink url="http://www.FreeBSD.org">www.freebsd.org</ulink></entry>
</row>
</tbody>
</tgroup>
</informaltable>

View file

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/eresources/chapter.sgml,v 1.30 1999/09/14 03:17:46 jim Exp $
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/eresources/chapter.sgml,v 1.31 1999/09/15 21:55:22 kuriyama Exp $
-->
<chapter id="eresources">
@ -239,6 +239,11 @@
<entry>Security issues</entry>
</row>
<row>
<entry>freebsd-security-notifications</entry>
<entry>Security notifications</entry>
</row>
<row>
<entry>freebsd-small</entry>
<entry>Using FreeBSD in embedded applications</entry>
@ -263,12 +268,11 @@
</tgroup>
</informaltable>
<para><emphasis>Limited lists:</emphasis> The following lists require
approval from <email>core@FreeBSD.org</email> to join, though anyone
is free to send messages to them which fall within the scope of their
charters. It is also a good idea establish a presence in the
technical lists before asking to join one of these limited
lists.</para>
<para><emphasis>Limited lists:</emphasis> The following lists are for
more specialized (and demanding) audiences and are probably not of
interest to the general public. It is also a good idea to establish a
presence in the technical lists before joining one of these limited
lists so that you'll understand the communications etiquette involved.</para>
<informaltable frame="none">
<tgroup cols="2">
@ -306,15 +310,15 @@
<entry>Installation development</entry>
</row>
<row>
<entry>freebsd-security-notifications</entry>
<entry>Security notifications</entry>
</row>
<row>
<entry>freebsd-user-groups</entry>
<entry>User group coordination</entry>
</row>
<row>
<entry>freebsd-www</entry>
<entry>Maintainers of <ulink url="http://www.FreeBSD.org">www.freebsd.org</ulink></entry>
</row>
</tbody>
</tgroup>
</informaltable>