Re: [Opensim-dev] versioning question

2009-09-04 Thread Stefan Andersson
0.6.6.10201 (Git:6cf610) (Dev) (interface version 5) /Stefan -Original Message- From: opensim-dev-boun...@lists.berlios.de [mailto:opensim-dev- boun...@lists.berlios.de] On Behalf Of Toni Alatalo Sent: den 3 september 2009 20:07 To: opensim-dev@lists.berlios.de Subject: Re: [Opensim-dev

Re: [Opensim-dev] versioning question

2009-09-04 Thread Toni Alatalo
that could make everyone happy :) /Stefan ~Toni -Original Message- From: opensim-dev-boun...@lists.berlios.de [mailto:opensim-dev- boun...@lists.berlios.de] On Behalf Of Toni Alatalo Sent: den 3 september 2009 20:07 To: opensim-dev@lists.berlios.de Subject: Re: [Opensim-dev

[Opensim-dev] versioning question

2009-09-03 Thread Paul Fishwick
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

Re: [Opensim-dev] versioning question

2009-09-03 Thread Gustavo Alberto Navarro Bilbao
Yes, is very dark. In our server we are using the last Diva's version from git, than works in our case better than the 0.6.6 downladed from the wiki, a service with 0.6.6 .10108, in OSGrid, an other with 0.6.6 .239a1 and other with modrex. The 0.6.6.6 in the console show the same interfase v 5,

Re: [Opensim-dev] versioning question

2009-09-03 Thread Justin Clark-Casey
The 'interface v5' part refers to the interface protocol between the region simulator and the grid (and defacto, between region simulators). It doesn't have anything at all to do with the OpenSim version (0.6.6). In principle, if you are running from a source repository update then the git

Re: [Opensim-dev] versioning question

2009-09-03 Thread Justin Clark-Casey
Paul Fishwick wrote: Justin: Justin Clark-Casey wrote: The 'interface v5' part refers to the interface protocol between the region simulator and the grid (and defacto, between region simulators). It doesn't have anything at all to do with the OpenSim version (0.6.6). OK In

Re: [Opensim-dev] versioning question

2009-09-03 Thread Paul Fishwick
I am using TortoiseGit and did a show log. When I do this, and show the graph clicking on the topmost message dated 9/2/2009, there is something that says Showing 10185 Revisions from Revision a82950 to 6cf610 not sure how to interpret this hexadecimal indexing. Should I consider 10185 to be the

Re: [Opensim-dev] versioning question

2009-09-03 Thread Justin Clark-Casey
Paul Fishwick wrote: I am using TortoiseGit and did a show log. When I do this, and show the graph clicking on the topmost message dated 9/2/2009, there is something that says Showing 10185 Revisions from Revision a82950 to 6cf610 It will be 6cf610, as this is only two revisions from the

Re: [Opensim-dev] versioning question

2009-09-03 Thread krtaylor
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

Re: [Opensim-dev] versioning question

2009-09-03 Thread Justin Clark-Casey
Paul Fishwick wrote: Justin Clark-Casey wrote: It will be 6cf610, as this is only two revisions from the bleeding edge. a82950 is the very oldest revision and 10185 might be the absolute number of revs. As long as there is a way that we know how to compare revisions. IE: The next

Re: [Opensim-dev] versioning question

2009-09-03 Thread Paul Fishwick
Justin Clark-Casey wrote: It will be 6cf610, as this is only two revisions from the bleeding edge. a82950 is the very oldest revision and 10185 might be the absolute number of revs. As long as there is a way that we know how to compare revisions. IE: The next revision to 6cf610 will be

Re: [Opensim-dev] versioning question

2009-09-03 Thread Dr Scofield
krtaylor wrote: 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