Late last week I found a script that tags each changeset that comes into the server with an increasing number. When you pull on master, you'll see these tags now flow down.
Because the nature of distributed version control, this is only going to give you a rough idea of forward or backward in time. Commits are made locally, and only when merged into the master server do they get an id. http://github.com/opensim/opensim/network will give an idea of the complex dance of changesets and why this is never going to be fully linear. But, that being said, the lack of a short version number like that is the #1 issue (by vocalness) that people were having with git. Hopefully this helps that. This short version number only means anything if you are getting your tree from the main opensim archive. -Sean -- __________________________________________________________________ Sean Dague Mid-Hudson Valley [email protected] Linux Users Group http://dague.net http://mhvlug.org There is no silver bullet. Plus, werewolves make better neighbors than zombies, and they tend to keep the vampire population down. __________________________________________________________________
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Opensim-dev mailing list [email protected] https://lists.berlios.de/mailman/listinfo/opensim-dev
