[haiku-development] Re: Haiku git migration status?
- From: Alexander von Gluck <kallisti5@xxxxxxxxxxx>
- To: <haiku-development@xxxxxxxxxxxxx>
- Date: Wed, 03 Aug 2011 14:14:11 -0500
On Wed, 3 Aug 2011 13:28:21 -0400, Ryan Leavengood wrote:
On Wed, Aug 3, 2011 at 12:34 PM, Brecht Machiels <brecht@xxxxxxxxxxx>
wrote:
Understandably, as Haiku is the *only* project tagging each and
every
changeset. This is clearly not the intended use for tags. But I
don't suppose
the few people in favor of the tags have changed their mind about it
yet? :)
I also think we should start tagging known stable commits with a real
version number (0.1.1.8 or whatever) which also shows up in
AboutSystem and do the "alpha release preparation" type tasks more
often.
+1. I still like the git describe version format I commented on a few
months ago:
$ git describe --abbrev=6
6.14.1-8-g903e90
that is versiontag-hash with a shortened hash. It directs you to the
code in reference to:
* the last major version
* the revision
they are in order by version, and gives you the commit.
Using the odd revision numbers tags on every commit seems like trying
to make
a DVCS something it isn't =\
Thanks!
-- Alex
Other related posts:
