SF.net SVN: matplotlib: [5181] branches/v0_91_maint/CODING_GUIDE

[<jd...@us...>]

Revision: 5181
          http://matplotlib.svn.sourceforge.net/matplotlib/?rev=5181&view=rev
Author:   jdh2358
Date:     2008-05-17 14:38:21 -0700 (Sat, 17 May 2008)

Log Message:
-----------
fixed some typos in the CODING_GUIDE

Modified Paths:
--------------
    branches/v0_91_maint/CODING_GUIDE

Modified: branches/v0_91_maint/CODING_GUIDE
===================================================================
--- branches/v0_91_maint/CODING_GUIDE	2008-05-17 21:32:33 UTC (rev 5180)
+++ branches/v0_91_maint/CODING_GUIDE	2008-05-17 21:38:21 UTC (rev 5181)
@@ -41,11 +41,13 @@
     MANIFEST.in.  This file determines what goes into the src
     distribution of the mpl build.
 
-  * Keep the maintenance branch and trunk in sync here it makes sense.
+  * Keep the maintenance branch and trunk in sync where it makes sense.
     If there is a bug on both that needs fixing, use svnmerge.py to
-    fix them.  http://www.orcaware.com/svn/wiki/Svnmerge.py.  The
+    keep them in sync.  http://www.orcaware.com/svn/wiki/Svnmerge.py.  The
     basic procedure is:
 
+      - install svnmerge.py in your PATH
+
       - get a svn copy of the branch (svn co
         https://matplotlib.svn.sourceforge.net/svnroot/matplotlib/branches/v0_91_maint)
         and the trunk (svn co
@@ -55,8 +57,9 @@
         it.  Make sure you svn upped on the trunk and have no local
         modifications, and then from the svn trunk do
 
-	# where these are the revision numbers.  ranges also acceptable
+	# where the NNN are the revision numbers.  ranges also acceptable
         > svnmerge.py merge -rNNN1,NNN2
+
 	# this file is automatically created by the merge command
         > svn commit -F svnmerge-commit-message.txt
 


This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.