db-derby-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From j..@apache.org
Subject svn commit: r430535 - in /db/derby/site/trunk: build/site/manuals/dita.html src/documentation/content/xdocs/manuals/dita.xml
Date Thu, 10 Aug 2006 21:22:05 GMT
Author: jta
Date: Thu Aug 10 14:22:04 2006
New Revision: 430535

URL: http://svn.apache.org/viewvc?rev=430535&view=rev
Log:
Updated Derby web site information on creating DITA patches so that 
it shows how to create a patch for just one book from the trunk.  
Also removed the paragraph about the Apache DB Project using cvs 
(the DB docs have since been updated).

Modified:
    db/derby/site/trunk/build/site/manuals/dita.html
    db/derby/site/trunk/src/documentation/content/xdocs/manuals/dita.xml

Modified: db/derby/site/trunk/build/site/manuals/dita.html
URL: http://svn.apache.org/viewvc/db/derby/site/trunk/build/site/manuals/dita.html?rev=430535&r1=430534&r2=430535&view=diff
==============================================================================
--- db/derby/site/trunk/build/site/manuals/dita.html (original)
+++ db/derby/site/trunk/build/site/manuals/dita.html Thu Aug 10 14:22:04 2006
@@ -328,18 +328,6 @@
 </p>
 <p> 
 
-<strong>Use 'svn diff' for patches, not 'cvs diff'</strong>
-
-</p>
-<p> 
-The Apache DB Project recommends using
-<a href="http://db.apache.org/source.html">cvs diff</a>
-output for creating patches,
-but Derby uses <span class="codefrag">svn</span>,
-so use '<span class="codefrag">svn diff</span>' instead.
-</p>
-<p> 
-
 <strong>How to create a patch</strong>
 
 </p>
@@ -396,7 +384,10 @@
 <li> 
 
 <p> 
-Make the patch.  Be sure to create the patch from the <span class="codefrag">trunk/</span>
directory.
+Make the patch.  
+Be sure to create the patch from the <span class="codefrag">trunk/</span> directory.
+The command shown below creates a patch with all the diffs in your
+working copy:
 </p> 
 
 <pre class="code">
@@ -404,6 +395,16 @@
 </pre>
 
 
+<p> 
+You can also create a patch with changes for just one book, as shown below:
+</p> 
+
+
+<pre class="code">
+svn diff src/tuning &gt; xyz.diff
+</pre>
+
+
 </li>
 
 <li>It will be necessary for the community to review your changes, and the best way
to do that is to see the HTML output that reflects your changes.  Since you have already created
HTML output when testing your changes, simply add the relevant HTML files along with the patch
file to a zip file.
@@ -475,7 +476,7 @@
 
 
 <p>
-<em>Last Updated: July 18, 2006</em>
+<em>Last Updated: August 10, 2006</em>
 </p>
 
 </div>

Modified: db/derby/site/trunk/src/documentation/content/xdocs/manuals/dita.xml
URL: http://svn.apache.org/viewvc/db/derby/site/trunk/src/documentation/content/xdocs/manuals/dita.xml?rev=430535&r1=430534&r2=430535&view=diff
==============================================================================
--- db/derby/site/trunk/src/documentation/content/xdocs/manuals/dita.xml (original)
+++ db/derby/site/trunk/src/documentation/content/xdocs/manuals/dita.xml Thu Aug 10 14:22:04
2006
@@ -152,18 +152,6 @@
 
 
 <p> 
-<strong>Use 'svn diff' for patches, not 'cvs diff'</strong>
-</p> 
-
-<p> 
-The Apache DB Project recommends using
-<a href="http://db.apache.org/source.html">cvs diff</a>
-output for creating patches,
-but Derby uses <code>svn</code>,
-so use '<code>svn diff</code>' instead.
-</p> 
-
-<p> 
 <strong>How to create a patch</strong>
 </p> 
 
@@ -204,12 +192,23 @@
 </li> 
 <li> 
 <p> 
-Make the patch.  Be sure to create the patch from the <code>trunk/</code> directory.
+Make the patch.  
+Be sure to create the patch from the <code>trunk/</code> directory.
+The command shown below creates a patch with all the diffs in your
+working copy:
 </p> 
 <source>
 svn diff &gt; xyz.diff
 </source>
 
+<p> 
+You can also create a patch with changes for just one book, as shown below:
+</p> 
+
+<source>
+svn diff src/tuning &gt; xyz.diff
+</source>
+
 </li>
 <li>It will be necessary for the community to review your changes, and the best way
to do that is to see the HTML output that reflects your changes.  Since you have already created
HTML output when testing your changes, simply add the relevant HTML files along with the patch
file to a zip file.
 </li>
@@ -274,6 +273,6 @@
 </section>
 
 
-<p><em>Last Updated: July 18, 2006</em></p>
+<p><em>Last Updated: August 10, 2006</em></p>
 </body>
 </document>



Mime
View raw message