I have been playing around with a solution for the sequential version reporting, but it is not as simple as it may seem. The best description of the problem and solution I have found is at:
http://michaelandlaura.org.uk/~michael/blog/index.php?id=379 The catch is that we appear to be using tag objects that are orphaned. To see an example of that, just run git show-ref on a clone tree for 0.6.6-release. The hash is shown, but then git log does not contain that hash, even when tracking the master. It seems that we need to switch to a slightly different policy of checking in and tagging at a release boundary and no orphaning that tag object. Alternatively, we could just lightweight tag the checkin that changes the release version file. Comments? Kurt Paul Fishwick wrote: > With the use of git or svn, what is the relationship between the > Version and the Build #? Once upon a time, we would do a > "show version" in the console, and it was very clear which specific > opensim version was being used. Now, it says: > > OpenSim 0.6.6 (Dev) (interface version 5) > > rather than something clearer (at least to me) like: > > OpenSim Version 10115 > > The problem is that I don't know which build to refer to as I would imagine > that the code base changes daily. Thanks. > > -p > > -- Kurt Taylor (Kurt Stringer) _______________________________________________ Opensim-dev mailing list Opensim-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/opensim-dev