changed old mailing lists from @lists.linuxdoc.org to @linuxdoc.org.

We're using ezmlm instead of majordomo now.
This commit is contained in:
markk 2000-12-04 17:09:14 +00:00
parent 1625a911ec
commit a0c21c2338
1 changed files with 21 additions and 15 deletions

View File

@ -28,7 +28,7 @@
<book>
<bookinfo>
<title>LDP Author Guide</title>
<pubdate>v3.4 1 Dec, 2000</pubdate>
<pubdate>v3.5 4 Dec, 2000</pubdate>
<author>
<firstname>Mark</firstname>
<othername>F.</othername>
@ -62,6 +62,12 @@
up to speed and writing. </para>
</abstract>
<revhistory>
<revision>
<revnumber>3.5</revnumber>
<date>Dec 4, 2000</date>
<authorinitials>mfk</authorinitials>
<revremark>Changed mailing list pointers to new lists.</revremark>
</revision>
<revision>
<revnumber>3.4</revnumber>
<date>Dec 1, 2000</date>
@ -211,7 +217,7 @@
<para>Thanks to everyone that gave comments as I was writing
this. This includes David Lawyer, Deb Richardson, Daniel Barlow,
Greg Ferguson, Mark Craig and other members of the
<email>ldp-discuss@lists.linuxdoc.org</EMAIL> list. Some
<email>discuss@linuxdoc.org</EMAIL> list. Some
sections I got from the <ulink
url="http://www.linuxdoc.org/HOWTO/">HOWTO Index</ulink> and the
sgmltools documentation. The sections on network access to CVS
@ -335,12 +341,12 @@
<para>If you are a new to the LDP and want to pick up an
unmaintained HOWTO or write a new HOWTO document, contact the
HOWTO coordinator at
<email>ldp-discuss@lists.linuxdoc.org</email>. This is to make
<email>discuss@linuxdoc.org</email>. This is to make
sure the HOWTO coordinator can know who is working on what
documentation.</para>
<para>Once that part is complete, you may write your
documentation in the format of your choice and submit a draft to
<email>ldp-submit@lists.linuxdoc.org</email> and the draft will
<email>submit@linuxdoc.org</email> and the draft will
be reviewed by an LDP volunteer. In a few short days you will
get the draft and comments from the volunteer. After applying
the comments, you may send this version to the ldp-submit list
@ -368,20 +374,20 @@
<title>Mailing Lists</title>
<para>There are a few mailing lists to subscribe to so you can
take part in how the LDP works. First is
<email>ldp-discuss@lists.linuxdoc.org</email>, which is the main
<email>discuss@linuxdoc.org</email>, which is the main
discussion group of the LDP. To subscribe, send a message with
the subject reading &quot;subscribe&quot; to
<email>ldp-discuss-request@lists.linuxdoc.org</email>. To
<email>discuss-subscribe@linuxdoc.org</email>. To
unsubscribe, send an e-mail with the subject of
&quot;unsubscribe&quot; to
<email>ldp-discuss-request@lists.linuxdoc.org</email>.</para>
<email>discuss-unsubscribe@linuxdoc.org</email>.</para>
<para>Another list is the
<email>ldp-docbook@lists.linuxdoc.org</email> list, which is for
<email>docbook@linuxdoc.org</email> list, which is for
markup or other questions about DocBook itself. If you run into
trouble with a particular markup tag, you can send your question
here for answers. You can subscribe to the DocBook list by
sending a "subscribe"message to
<email>ldp-docbook-request@lists.linuxdoc.org</email>.</para>
sending a "subscribe" message to
<email>docbook-subscribe@linuxdoc.org</email>.</para>
</section>
</chapter>
@ -658,7 +664,7 @@ $_toolroot/dtd/docbook/catalog</command> <co id="export">
to validate your document while writing.</para>
<para>For users of Emacs, it's a great way to go, and many
believe it to allow more versatility than any other SGML
documentation tool. It works with DocBook,LinuxDoc and other
documentation tool. It works with DocBook, LinuxDoc and other
DTDs equally well.</para>
<section>
<title> Writing SGML using PSGML </title>
@ -1410,7 +1416,7 @@ $_toolroot/dtd/docbook/catalog</command> <co id="export">
<para> Once your LDP document has been carefully reviewed, you
can release your document to the LDP. Send an e-mail with the
SGML source code as an attachment (you may gzip it if you like)
to <email>ldp-submit@lists.linuxdoc.org</email>. </para>
to <email>submit@linuxdoc.org</email>. </para>
<para> Be sure to include the name of your HOWTO in the subject
line, and use the body to outline changes you've made and attach
@ -1428,7 +1434,7 @@ $_toolroot/dtd/docbook/catalog</command> <co id="export">
<para>If you are using the LDP CVS tree while developing
your document, the LDP will still need to be notified when your
document is ready to be published. E-mail should be sent to
<email>ldp-submit@lists.linuxdoc.org</email>. Indicate
<email>submit@linuxdoc.org</email>. Indicate
the title of your document and the relative path to the
file(s) in the LDP CVS tree within your message. </para>
</section>
@ -1493,7 +1499,7 @@ $_toolroot/dtd/docbook/catalog</command> <co id="export">
</question>
<answer>
<para> Contact the author of the document, or the LDP
coordinator at <email>ldp-discuss@lists.linuxdoc.org</email> and
coordinator at <email>discuss@linuxdoc.org</email> and
mention the problem and how you think it needs to be
fixed. </para>
</answer>
@ -1511,7 +1517,7 @@ $_toolroot/dtd/docbook/catalog</command> <co id="export">
be easier for you to maintain the HOWTO. If you run into
questions,you can always drop a line to the LDP volunteer or the
LDP Docbook list
at <email>ldp-docbook@lists.linuxdoc.org</email>.</para>
at <email>docbook@linuxdoc.org</email>.</para>
</answer>
</qandaentry>
</qandaset>