From 9fefb159c4e57effe41ecbc59000789e3db808ac Mon Sep 17 00:00:00 2001
From: serek <>
Date: Sat, 26 Jan 2002 20:31:11 +0000
Subject: [PATCH] - Changing the suggested way of notification for ready for
 publish documets. Ready for publish :-).

---
 LDP/guide/docbook/LDP-Author-Guide/cvs.xml | 22 ++++++++++++++++++----
 1 file changed, 18 insertions(+), 4 deletions(-)

diff --git a/LDP/guide/docbook/LDP-Author-Guide/cvs.xml b/LDP/guide/docbook/LDP-Author-Guide/cvs.xml
index b41066ee..34a415c5 100644
--- a/LDP/guide/docbook/LDP-Author-Guide/cvs.xml
+++ b/LDP/guide/docbook/LDP-Author-Guide/cvs.xml
@@ -140,10 +140,24 @@ guide/docbook/YOURGUIDE</command>
         discuss list. </para>
         <para>If you are using the LDP CVS tree while developing your
         document, the LDP will need to be notified when your
-        document is ready to be published. E-mail should be sent to
-        <email>submit@linuxdoc.org</email>. Indicate within the message
-        the title of your document and the relative path to the
-        file(s) in the LDP CVS tree. </para>
+	document is ready to be published. There are two methods:</para>
+
+	<itemizedlist>
+          <listitem>
+		<para>You can add to the CVS commit message a text similar to 
+		 "- ready for publish."</para>
+	  </listitem>
+ 	  <listitem>
+		<para>You can notify us by e-mail. E-mail should be sent to
+        	<email>submit@linuxdoc.org</email>. Indicate within the message
+        	the title of your document and the relative path to the
+		file(s) in the LDP CVS tree. </para>
+          </listitem>
+  	</itemizedlist>
+
+        <para>We prefer CVS users to trigger a publishing operation thru their
+        'commits' message.</para>
+
       </section>
 
       <section id="addnewcvs">