Return-Path: 
 <cocoon-cvs-return-5166-apmail-xml-cocoon-cvs-archive=xml.apache.org@xml.apache.org>
Delivered-To: apmail-xml-cocoon-cvs-archive@xml.apache.org
Received: (qmail 65069 invoked by uid 500); 30 Jan 2002 14:19:14 -0000
Mailing-List: contact cocoon-cvs-help@xml.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cocoon-dev@xml.apache.org
list-help: <mailto:cocoon-cvs-help@xml.apache.org>
list-unsubscribe: <mailto:cocoon-cvs-unsubscribe@xml.apache.org>
list-post: <mailto:cocoon-cvs@xml.apache.org>
Delivered-To: mailing list cocoon-cvs@xml.apache.org
Received: (qmail 65060 invoked by uid 500); 30 Jan 2002 14:19:14 -0000
Delivered-To: apmail-xml-cocoon2-cvs@apache.org
Date: 30 Jan 2002 14:19:13 -0000
Message-ID: <20020130141913.45101.qmail@icarus.apache.org>
From: crossley@apache.org
To: xml-cocoon2-cvs@apache.org
Subject: cvs commit: xml-cocoon2/src/documentation/xdocs contrib.xml
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N

crossley    02/01/30 06:19:13

  Modified:    src/documentation/xdocs contrib.xml
  Log:
  Clarify patch submission procedure. Better URL for OpenSP validating parser.
  
  Revision  Changes    Path
  1.3       +6 -5      xml-cocoon2/src/documentation/xdocs/contrib.xml
  
  Index: contrib.xml
  ===================================================================
  RCS file: /home/cvs/xml-cocoon2/src/documentation/xdocs/contrib.xml,v
  retrieving revision 1.2
  retrieving revision 1.3
  diff -u -r1.2 -r1.3
  --- contrib.xml	20 Jan 2002 23:59:38 -0000	1.2
  +++ contrib.xml	30 Jan 2002 14:19:13 -0000	1.3
  @@ -360,8 +360,9 @@
     <p>
      When you are sure about your proposed patch, then please submit it
      via Bugzilla, rather than as email to <code>cocoon-dev</code>.
  -   Be sure to add [Patch] to the summary line, as this enables the automatic
  -   patch alert system to keep track of it.
  +   Be sure to add [PATCH] to the summary line, as this enables the automatic
  +   patch alert system to keep track of it. If you do not follow this procedure,
  +   then unfortunately your patch may be over-looked.
     </p>
   
     <p>
  @@ -409,7 +410,7 @@
      </li>
      <li>
       Prepend your email subject line with a marker when that is appropriate,
  -    e.g. <code>[Patch]</code>, <code>[Proposal]</code>, 
  +    e.g. <code>[Vote]</code>, <code>[Proposal]</code>, 
       <code>[RT]</code> (Random Thought which quickly blossom into research
       topics :-), <code>[STATUS]</code> (development status of a certain
       facility).
  @@ -419,11 +420,11 @@
       matter, use a 
       <link href="http://www.oasis-open.org/cover/">validating parser</link>
       (one that is tried and true is
  -    <link href="http://www.jclark.com/sp/">SP/nsgmls</link>).
  +    <link href="http://openjade.sourceforge.net/">OpenSP/onsgmls</link>).
       This procedure will detect errors without having to go through the whole
       <code>build docs</code> process to find them. Do not expect Cocoon
       or the build system to detect the validation errors for you - they can
  -    do it, but that is not their purpose. (Anyway, nsgmls validation error
  +    do it, but that is not their purpose. (Anyway, onsgmls validation error
       messages are more informative.)
      </li>
      <li>
  
  
  

----------------------------------------------------------------------
In case of troubles, e-mail:     webmaster@xml.apache.org
To unsubscribe, e-mail:          cocoon-cvs-unsubscribe@xml.apache.org
For additional commands, e-mail: cocoon-cvs-help@xml.apache.org