This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author DLitz
Recipients DLitz, Natalia, barry, eric.araujo, piotr, tarek
Date 2012-12-10.16:39:24
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1355157564.99.0.188680499288.issue14894@psf.upfronthosting.co.za>
In-reply-to
Content
"git describe --tags --always" will return a bare commit id if there is no previous tag.  This is pretty common to have when you're working on a new package that hasn't been released yet:

$ git init
Initialized empty Git repository in /tmp/repo/.git/
$ touch foo
$ git add foo
$ git commit -m 'Initial commit'
[master (root-commit) cd7dd74] Initial commit
 0 files changed
 create mode 100644 foo
$ git describe --tags --always
cd7dd74
$ git tag v1.0
$ git describe --tags --always
v1.0
History
Date User Action Args
2012-12-10 16:39:25DLitzsetrecipients: + DLitz, barry, tarek, eric.araujo, piotr, Natalia
2012-12-10 16:39:24DLitzsetmessageid: <1355157564.99.0.188680499288.issue14894@psf.upfronthosting.co.za>
2012-12-10 16:39:24DLitzlinkissue14894 messages
2012-12-10 16:39:24DLitzcreate