diff --git a/Doc/Devel/engineering.html b/Doc/Devel/engineering.html index 2e78fbe35..c12eb1328 100644 --- a/Doc/Devel/engineering.html +++ b/Doc/Devel/engineering.html @@ -25,7 +25,7 @@
-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:
-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). -@@ -137,8 +137,6 @@ a SVN revision tag like this: * This file defines ... * ----------------------------------------------------------------------------- */ -static char cvs[] = "$Id$"; - #include "swig.h" /* Declarations */ @@ -159,12 +157,6 @@ static int avariable;
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,10 +371,10 @@ making your changes.
These are largely covered in the main documentation in the Extending.html file.
-11. SVN Tagging Conventions
+11. Git Tagging Conventions
-Use svn tag to declare some set of file revisions as related in some
+Use git tag 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!
@@ -390,10 +382,10 @@ let's hope they stay that way!
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.
-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:
diff --git a/Lib/python/pyname_compat.i b/Lib/python/pyname_compat.i index b5acca955..4026805ba 100644 --- 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 index d3c4b8c47..c6259916b 100644 --- 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 index 0f64235fb..9229274c2 100644 --- 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-@PACKAGE_VERSION@.tar.gz swig-@PACKAGE_VERSION@ && rpmbuild -tb swig-@PACKAGE_VERSION@.tar.gz # @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