Replace references to Subversion with Git

jaeandersson · Jan 12, 2013 · a6d456a · a6d456a
1 parent 7841a0d
commit a6d456a
Show file tree

Hide file tree

Showing 5 changed files with 16 additions and 26 deletions.
diff --git a/Doc/Devel/engineering.html b/Doc/Devel/engineering.html
@@ -25,7 +25,7 @@ <h2>Table of Contents</h2>
 <li><a name="i8" href="#8">8. Naming Conventions</a>
 <li><a name="i9" href="#9">9. Visibility</a>
 <li><a name="i10" href="#10">10. Miscellaneous Coding Guidelines</a>
-<li><a name="i11" href="#11">11. SVN Tagging Conventions</a>
+<li><a name="i11" href="#11">11. Git Tagging Conventions</a>
 </ul>
 
 <a name="1" href="#i1">
@@ -119,8 +119,8 @@ <h2>5. File Structure </h2>
 creating two files that differ in case-only.
 
 <p>
-Each file should include a short abstract, license information and
-a SVN revision tag like this:
+Each file should include a short abstract and license information
+like this:
 
 <blockquote>
 <pre>
@@ -137,8 +137,6 @@ <h2>5. File Structure </h2>
  * This file defines ...
  * ----------------------------------------------------------------------------- */
 
-static char cvs[] = "&#36Id&#36";
-
 #include "swig.h"
 
 /* Declarations */
@@ -159,12 +157,6 @@ <h2>5. File Structure </h2>
 </pre>
 </blockquote>
 
-The SVN revision tag should be placed into a static string as shown
-above mangled with the name of the file.
-This adds the revision information to the SWIG executable and
-makes it possible to extract version information from a raw binary
-(sometimes useful in debugging).  
-
 <p>
 As a general rule, files start to get unmanageable once they exceed
 about 2000 lines.  Files larger than this should be broken up into
@@ -379,21 +371,21 @@ <h2>10. Miscellaneous Coding Guidelines</h2>
 These are largely covered in the main documentation in the Extending.html file.
 
 <a name="11" href="#i11">
-<h2>11. SVN Tagging Conventions</h2>
+<h2>11. Git Tagging Conventions</h2>
 </a>
 
-Use <tt>svn tag</tt> to declare some set of file revisions as related in some
+Use <tt>git tag</tt> to declare some set of file revisions as related in some
 symbolic way.  This eases reference, retrieval and manipulation of these files
 later.  At the moment (2001/01/16 14:02:53), the conventions are very simple;
 let's hope they stay that way!
 
 <p>
 There are two types of tags, internal (aka personal) and external.
 Internal tags are used by SWIG developers primarily, whereas external
-tags are used when communicating with people w/ anonymous svn access.
+tags are used when communicating with people w/ anonymous git access.
 <ul>
 <li> Internal tags should start with the developer name and a hyphen.
-<li> External tags should start with "v-".
+<li> External tags should start with "rel-".
 </ul>
 
 That's all there is to it.  Some example tags:
@@ -402,10 +394,8 @@ <h2>11. SVN Tagging Conventions</h2>
 <li> ttn-pre-xml-patch
 <li> ttn-post-xml-patch
 <li> ttn-going-on-vacation-so-dutifully-tagging-now
-<li> v-1-3-a37-fixes-bug-2432
-<li> v-1-3-a37-fixes-bug-2433
-<li> v-1-3-a37-fixes-bug-2432-again
-<li> v-1-3-a37-release
+<li> rel-1.3.40
+<li> rel-2.0.9
 </ul>
 
 <hr>

diff --git a/Doc/Manual/Preface.html b/Doc/Manual/Preface.html
@@ -93,7 +93,7 @@ <H2><a name="Preface_nn5"></a>1.3 SWIG resources</H2>
 </p>
 
 <p>
-Subversion access to the latest version of SWIG is also available.  More information 
+Git and Subversion access to the latest version of SWIG is also available.  More information 
 about this can be obtained at:
 </p>
 

diff --git a/Lib/python/pyname_compat.i b/Lib/python/pyname_compat.i
@@ -20,8 +20,8 @@
 * However, this file may be removed in future release of SWIG, so using this file to
 * keep these inappropriate names in your SWIG interface file is also not recommended.
 * Instead, we provide a simple tool for converting your interface files to
-* the new naming convention. You can download the tool here:
-* https://swig.svn.sourceforge.net/svnroot/swig/trunk/Tools/pyname_patch.py
+* the new naming convention. You can get the tool from the SWIG distribution:
+* Tools/pyname_patch.py
 */
 
 %fragment("PySequence_Base", "header", fragment="SwigPySequence_Base") {}

diff --git a/Makefile.in b/Makefile.in
@@ -494,7 +494,7 @@ dist:
 
 srcrpm:
 	rm -fr $(srpm) $(srpm).src.rpm
-	echo "TODO: update to use svn instead of cvs"
+	echo "TODO: update to use git instead of cvs"
 	cvs export -d $(srpm) -r HEAD SWIG
 	cp swig.spec $(srpm)
 	tar -cf - $(srpm) | gzip --best > $(srpm).tar.gz
@@ -503,7 +503,7 @@ srcrpm:
 
 # Update the autoconf files for detecting host/targets. Automake will do this in
 # version 1.10 for our case of not having a top level Makefile.am. Until then we
-# can fetch them manually and will have to commit them to SVN.
+# can fetch them manually and will have to commit them to Git.
 configfiles:
 	wget ftp://ftp.gnu.org/pub/gnu/config/config.guess -O Tools/config/config.guess
 	chmod a+x Tools/config/config.guess

diff --git a/swig.spec.in b/swig.spec.in
@@ -1,4 +1,4 @@
-# You can build the package from SVN using something like:
+# You can build the package from Git using something like:
 # tar -czf swig-@[email protected] swig-@PACKAGE_VERSION@ && rpmbuild -tb swig-@[email protected]
 # @configure_input@
 
@@ -36,7 +36,7 @@ its parse tree in the form of XML and Lisp s-expressions.
 %setup -q -n %{name}-%{version}
 
 %build
-# so we can build package from SVN source too
+# so we can build package from Git source too
 [ ! -r configure ] && ./autogen.sh
 %configure
 make
-Original file line number
+Diff line change
@@ Expand Up / @@ -93,7 +93,7 @@ <H2><a name="Preface_nn5"></a>1.3 SWIG resources</H2> @@
     </p>
     <p>
-    Subversion access to the latest version of SWIG is also available.  More information
+    Git and Subversion access to the latest version of SWIG is also available.  More information
     about this can be obtained at:
     </p>
@@ Expand Down @@