httpd-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From rbo...@apache.org
Subject svn commit: r1326168 - in /httpd/site/trunk: docs/docs-project/svn.html xdocs/docs-project/svn.xml
Date Sat, 14 Apr 2012 18:03:55 GMT
Author: rbowen
Date: Sat Apr 14 18:03:55 2012
New Revision: 1326168

URL: http://svn.apache.org/viewvc?rev=1326168&view=rev
Log:
Add a mention of 'svn up' so that this is, in fact, all that they'll
need to submit a patch.

Modified:
    httpd/site/trunk/docs/docs-project/svn.html
    httpd/site/trunk/xdocs/docs-project/svn.xml

Modified: httpd/site/trunk/docs/docs-project/svn.html
URL: http://svn.apache.org/viewvc/httpd/site/trunk/docs/docs-project/svn.html?rev=1326168&r1=1326167&r2=1326168&view=diff
==============================================================================
--- httpd/site/trunk/docs/docs-project/svn.html [utf-8] (original)
+++ httpd/site/trunk/docs/docs-project/svn.html [utf-8] Sat Apr 14 18:03:55 2012
@@ -100,8 +100,15 @@ the resources you might need to verify y
  </tr>
  <tr><td>
   <blockquote>
-<p>Once you have a checkout, creating a patch takes three steps.</p>
+<p>Once you have a checkout, creating a patch takes four steps.</p>
 <ol>
+<li><p>Update your checkout, to be sure that you have the latest changes 
+in the repository, in case someone else has changed something since the
+last time you worked on the docs:</p>
+<example>
+svn update
+</example>
+</li>
 <li><p>Edit the file that you wish to modify. Make the desired changes,
 and then save your changes.</p></li>
 <li><p>At the command line, type the following to create a patch
@@ -134,7 +141,11 @@ svn diff mod_rewrite.xml &gt; mod_rewrit
   <blockquote>
 <p>See also the document on <a href="docsformat.html">documentation
 format and transformation</a> for details about verifying that your
-changes are complient with our documentation format and standards.</p>
+changes are complient with our documentation format and standards. In
+your email message, indicate what branch of the code the patch is
+against (trunk, 2.4, 2.2, etc.) what file(s) are affected, and what
+change you are making. If it's in reference to a specific bug ticket,
+mention that, too.</p>
   </blockquote>
  </td></tr>
 </table>

Modified: httpd/site/trunk/xdocs/docs-project/svn.xml
URL: http://svn.apache.org/viewvc/httpd/site/trunk/xdocs/docs-project/svn.xml?rev=1326168&r1=1326167&r2=1326168&view=diff
==============================================================================
--- httpd/site/trunk/xdocs/docs-project/svn.xml [utf-8] (original)
+++ httpd/site/trunk/xdocs/docs-project/svn.xml [utf-8] Sat Apr 14 18:03:55 2012
@@ -33,9 +33,16 @@ the resources you might need to verify y
 <section>
 <title>Creating a patch</title>
 
-<p>Once you have a checkout, creating a patch takes three steps.</p>
+<p>Once you have a checkout, creating a patch takes four steps.</p>
 
 <ol>
+<li><p>Update your checkout, to be sure that you have the latest changes 
+in the repository, in case someone else has changed something since the
+last time you worked on the docs:</p>
+<example>
+svn update
+</example>
+</li>
 <li><p>Edit the file that you wish to modify. Make the desired changes,
 and then save your changes.</p></li>
 <li><p>At the command line, type the following to create a patch
@@ -62,7 +69,11 @@ svn diff mod_rewrite.xml &gt; mod_rewrit
 
 <p>See also the document on <a href="docsformat.html">documentation
 format and transformation</a> for details about verifying that your
-changes are complient with our documentation format and standards.</p>
+changes are complient with our documentation format and standards. In
+your email message, indicate what branch of the code the patch is
+against (trunk, 2.4, 2.2, etc.) what file(s) are affected, and what
+change you are making. If it's in reference to a specific bug ticket,
+mention that, too.</p>
 </section>
 
 </body>



Mime
View raw message