Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo


#230 Use last changed revsion for svn revision

Mark Miesfeld
Mark Miesfeld

svn info provides the "Last Changed Rev:" number which is a better revision number than "Revision:"

Take for example a recent situation in the 3.x interpreter source. The last commit to the interpreter source was 715, but several doc commits were made after that. svn info showed this:

[root@Falcon interpreter.now]# svn info
Path: .
URL: https://oorexx.svn.sourceforge.net/svnroot/oorexx/interpreter-3.x/trunk
Repository Root: https://oorexx.svn.sourceforge.net/svnroot/oorexx
Repository UUID: 5c7345e9-2c1c-0410-8966-b4899360e60d
Revision: 718
Node Kind: directory
Schedule: normal
Last Changed Author: wdashley
Last Changed Rev: 715

The revsion level that the interpreter code was at was really 715, but the last commit was 718. 716 - 718 were all commits to the doc portion of the repository, the interpreter code was not changed.

Using Last Changed Revision rather than Revsion will give us a more accurate revision number.


  • Mark Miesfeld
    Mark Miesfeld

    Although I'm still in favor of this, it appears no one else is. So, I'm closing it.



Cancel   Add attachments