On Jun 29, 5:30 am, Paul Miller <[email protected]> wrote: > On Jun 28, 6:21 pm, Dustin <[email protected]> wrote: > > > There's a tender issue open for this. The right thing to do is for > > people to tag correctly and then just use git describe. It's not > > particularly hard, either. > > Maybe I'm being dense, but I don't see how 'git describe' helps. You > mean the tarball filename should contain the git describe (rather than > the commit id)?
Yes. That's what we do for memcached. If I were to make dist right now, it'd look like this: memcached-1.4.0-rc1-3-gd7c78ce.tar.gz The next tag is 1.4.0, which will produce a file that looks like this: memcached-1.4.0.tar.gz That id is also built into the binary and used for the internal version number. That is, the entire version numbering of memcached is driven from a single ``git tag -s'' --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "GitHub" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/github?hl=en -~----------~----~----~----~------~----~------~--~---
