+1 The git hashes are much more than a visual commit identifier, they are the hash of the commit and ensure that the content in the commit is valid. The tags can be easily changed and should not be relied on to point to a particular commit. For keeping up with the timeline of commits, the commit timestamp is good. I usually tag archives and releases with the short hash and timestamp with this command ...
`git log -n 1 --pretty=format:%h-%ct` which gives something like: 3aa9e78-1435144114 and contains both enough of the hash to identify the commit along with the unix timestamp of the commit time. -BlueWall On Sat, 2015-09-12 at 15:23 -0700, Diva Canto wrote: > Hi everyone, > > I know this has been discussed a few times before, but the automatic > tags on every git commit are becoming a heavy burden. Today we talked > again about stopping doing that. But rather than stopping the tags > without replacement, a suggestion has been made to provide a web page > that converts from git hashes to build numbers, so that everyone can > still have an idea of sequential line of development. > > Any objections? > > Diva > > _______________________________________________ > Opensim-dev mailing list > [email protected] > http://opensimulator.org/cgi-bin/mailman/listinfo/opensim-dev _______________________________________________ Opensim-dev mailing list [email protected] http://opensimulator.org/cgi-bin/mailman/listinfo/opensim-dev
