On Fri, Oct 2, 2009 at 10:13 AM, Jeremy Hinegardner <[email protected]> wrote: ... > jer...@stiletto:~/repos/git/beanstalkd master % git describe --match v1.1 > v1.1-171-g9f71603 > jer...@stiletto:~/repos/git/beanstalkd master % git describe --match v1.2 > v1.2-60-g9f71603 > jer...@stiletto:~/repos/git/beanstalkd master % git describe --match v1.3 > v1.3-55-g9f71603 > ... > Its not perfect, if you have the same number of commits from a tag in two > different branches, you could have 2 spec files that had the same > name-version-release but would be two different rpms.
Isn't that hash prefix at the end (g9f71603) the current commit? It's the same in your example because you were trying to demonstrate git-describe, but in real life, the output of the same git-describe on two different commits, even with the same # of commits to the same ancestor tag, would have different hashes. Right? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "beanstalk-talk" 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/beanstalk-talk?hl=en -~----------~----~----~----~------~----~------~--~---
