#50758 [Opn]: [FR] Print revision number

From: Date: Fri, 15 Jan 2010 12:29:11 +0000
Subject: #50758 [Opn]: [FR] Print revision number
References: 1  Groups: php.doc.bugs 
Request: Send a blank email to doc-bugs+get-3714@lists.php.net to get a copy of this message
ID: 50758 Updated by: rquadling@php.net Reported By: hannes dot magnusson at gmail dot com Status: Open Bug Type: Doc Build problem Operating System: * PHP Version: 5.3SVN-2010-01-14 (snap) New Comment: If $Revision became $Id in the XML files (a one of BIG hit with all that that entails for translators), then a PI could extract the elements from the $Id entry. But that is a massive issue for translators. Unless there is a way to alter a file in SVN _WITHOUT_ it updating the Revision - which, thinking about it, sorts of invalidates the whole Revision process really. But, running ... svn info phpdoc/modules/doc-all/en outputs ... Path: phpdoc\modules\doc-all\en URL: http://svn.php.net/repository/phpdoc/en/trunk Repository Root: http://svn.php.net/repository Repository UUID: c90b9560-bf6c-de11-be94-00142212c4b1 Revision: 293572 Node Kind: directory Schedule: normal Last Changed Author: stas Last Changed Rev: 293566 Last Changed Date: 2010-01-15 01:58:44 +0000 (Fri, 15 Jan 2010) Processing that should be fairly easy. Previous Comments: ------------------------------------------------------------------------ [2010-01-15 08:26:34] bjori@php.net I was just thinking about the current checkout revision, not per-file. I think figuring out the revision/last modification date for every single file would be a bit to much hassle. ------------------------------------------------------------------------ [2010-01-15 00:15:16] rquadling@php.net As the manual is a collection of a LOT of files, each page would have a different date though surely? ------------------------------------------------------------------------ [2010-01-14 21:55:27] hannes dot magnusson at gmail dot com Description: ------------ Currently the PHP manual prints the build date (i.e. when the manual was rendered), but that doesn't help figuring out how up2date the manual actually is. If we could print out revision number, or even figuring out the last 'svn up' timestamp, and print that with the builddate.. maybe introduce a PI for it? <?getSVNRevision?> or something? ------------------------------------------------------------------------ -- Edit this bug report at http://bugs.php.net/?id=50758&edit=1

« previous php.doc.bugs (#3714) next »