nikhilgupta10
commented
8 years ago nikhilgupta10 imported these comments from Sourceforge: The user dchassin does not exist anymore. Therefore assigning this to afisher1. "dchassin":For example, if you checked out and built ticket 716 today you would get rev 4745 when querying the version from the command line. But you would get the same version if you checked out and built ticket 797 today. You should see rev 4716 for ticket 716 (coincidence that 716 is in both), and rev 4724 for ticket 797. Rev 4745 is associated with ticket 533.
The version info is very confusing are quasi-useless the way it's implemented now. It would greatly improve support if the rev number were accurate.
Also, the change in win32 and x64 needs to be made in utilities/buildnum.bat. ,
"dchassin":Fixed, validated and posted as of r4758. From now on version will be report last change on the branch they come from, not last change on the entire repo.,
"dchassin":- status: new --> assigned
- assigned_to: Andy Fisher
- Milestone: 1.0 --> Unscheduled
-
Resolution: none --> validate ,
"dchassin":Posted to trunk at r4758. Ready to apply to branch/3.1.,
"jcfuller":- Milestone: Unscheduled --> Version 3.2 RC1
-
Priority: none --> critical ,
"dchassin":I just posted to trunk a fix of the Linux/Mac build process to address this problem.,
"dchassin":Be very carefully about copying the code to recorder. There are differences in how they work and in my opinion there's a much easier way to do than what's in collector.,
"dchassin":This fix was applied to 3.2.,
"dchassin":- status: assigned --> closed
- assigned_to: Andy Fisher --> David P. Chassin
- Milestone: Version 3.2 RC1 --> Knothole Interim
-
Resolution: validate --> fixed ,
"dchassin":Fixed in trunk.,
It always returns the last rev over the entire project, not the last rev for the particular branch. Recommend changing core/Makefile.mk to search for \Last Changed Rev:\ instead of \Revision:.,