Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG  Not logged in ELOG logo
icon5.gif   svn revision number in the source, posted by Steve Jones on Tue Feb 21 19:25:28 2006 
    icon2.gif   Re: svn revision number in the source, posted by Stefan Ritt on Tue Feb 21 20:24:18 2006 
       icon2.gif   Re: svn revision number in the source, posted by Steve Jones on Tue Feb 21 21:01:22 2006 
          icon2.gif   Re: svn revision number in the source, posted by Stefan Ritt on Tue Feb 21 21:17:13 2006 
             icon14.gif   Re: svn revision number in the source, posted by Steve Jones on Tue Feb 21 21:58:16 2006 
                icon2.gif   Re: svn revision number in the source, posted by Steve Jones on Tue Feb 21 22:13:40 2006 
                   icon2.gif   Re: svn revision number in the source, posted by Stefan Ritt on Tue Feb 21 22:33:32 2006 
                      icon7.gif   Re: svn revision number in the source, posted by Steve Jones on Tue Feb 21 22:37:14 2006 
Message ID: 1704     Entry time: Tue Feb 21 21:17:13 2006     In reply to: 1703     Reply to this: 1705
Icon: Reply  Author: Stefan Ritt  Author Email: stefan.ritt@psi.ch 
Category: Question  OS: All  ELOG Version: 2.6.1 
Subject: Re: svn revision number in the source 

Steve Jones wrote:
So, when we go to the download section and download directly from there, that is not "committed" source? I ask because the revision id there is not set to anything that I can see.


Can you be a bit more specific? What do you download? The Windows binaries, the Linux RPM? Or from the Subversion repository? The current version in the repository, which you can download here, contains in the file elogd.c following line 8:
   $Id: elogd.c 1660 2006-02-17 19:48:12Z ritt $

This tells you that this is revision 1660, committed on Feb. 17 by myself. So what is the problem?
ELOG V3.1.5-fe60aaf