[Scummvm-cvs-logs] SF.net SVN: scummvm:[39380] scummvm/trunk/tools/update-version.pl

fingolfin at users.sourceforge.net fingolfin at users.sourceforge.net
Sat Mar 14 02:45:01 CET 2009


Revision: 39380
          http://scummvm.svn.sourceforge.net/scummvm/?rev=39380&view=rev
Author:   fingolfin
Date:     2009-03-14 01:45:00 +0000 (Sat, 14 Mar 2009)

Log Message:
-----------
removed obsolete comment

Modified Paths:
--------------
    scummvm/trunk/tools/update-version.pl

Modified: scummvm/trunk/tools/update-version.pl
===================================================================
--- scummvm/trunk/tools/update-version.pl	2009-03-14 01:44:53 UTC (rev 39379)
+++ scummvm/trunk/tools/update-version.pl	2009-03-14 01:45:00 UTC (rev 39380)
@@ -38,18 +38,6 @@
 	backends/platform/psp/README.PSP
 	);
 
-# The following files also contain version data and should possible be modified
-# by this script, too. However, the relevant parts of these documentation files
-# talk about "Known issues", and I am not sure if we really should automatically
-# update these... in fact, it might be better to factor out that information and
-# put it into a single "ISSUES" or "KNOWN_ISSUES" file like other projects do...
-# * README
-# * doc/03_10.tex / doc/03_11.tex  (depends on which branch you look at <shudder>)
-
-# TODO: The following substituion table could easily be extended. In particular
-# one could add a function similar to autoconf's AC_SUBST:
-#    addSubst(FOO)
-# which would automagically add FOO => $FOO to the table
 my %subs = (
 	VER_MAJOR	=>	$VER_MAJOR,
 	VER_MINOR	=>	$VER_MINOR,


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




More information about the Scummvm-git-logs mailing list