forrest-svn mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From cross...@apache.org
Subject svn commit: r409548 - /forrest/trunk/site-author/content/xdocs/howto-dev.xml
Date Fri, 26 May 2006 03:42:05 GMT
Author: crossley
Date: Thu May 25 20:42:05 2006
New Revision: 409548

URL: http://svn.apache.org/viewvc?rev=409548&view=rev
Log:
Add #svn-find-break to explain how to update svn backwards.

Modified:
    forrest/trunk/site-author/content/xdocs/howto-dev.xml

Modified: forrest/trunk/site-author/content/xdocs/howto-dev.xml
URL: http://svn.apache.org/viewvc/forrest/trunk/site-author/content/xdocs/howto-dev.xml?rev=409548&r1=409547&r2=409548&view=diff
==============================================================================
--- forrest/trunk/site-author/content/xdocs/howto-dev.xml (original)
+++ forrest/trunk/site-author/content/xdocs/howto-dev.xml Thu May 25 20:42:05 2006
@@ -192,6 +192,39 @@
         </p>
       </section>
 
+      <section id="svn-find-break">
+        <title>Updating svn backwards to find where something broke</title>
+        <p>Sometimes the addition of new features will break something. Often
+          it is difficult to find where the break occurred and what caused it.
+          Updating your svn backwards will enable this.
+        </p>
+        <p>
+          Look at the svn@ mail list to guess which change might be the culprit,
+          e.g. svn revision 406862.
+        </p>
+        <source>
+Update backwards to just before the upgrade:
+svn update -r 406861
+... do 'build clean; build' and test.
+
+Go back further if it still doesn't work.
+After success, start upgrading forward.
+
+Looking at the svn@ mailing list shows that
+could jump forward past minor changes such as doc edits.
+e.g. just after the upgrade:
+svn update -r 406863
+... do 'build clean; build' and test.
+
+If it still works, move a bit further on:
+svn update -r 407260
+... do 'build clean; build' and test.
+
+After finding the break, move back to head of trunk
+svn update -r HEAD.
+        </source>
+      </section>
+
       <section id="svn-patch">
         <title>Creating patches</title>
         <p>See 



Mime
View raw message