Re: Deciding between Git/Mercurial
- From
Martin Langhoff <martin.langhoff@gmail.com>
- Date
- Oct 22, 2009, 08:01 UTC
- Message-ID
- <46a038f90910220101h4f3ecf22x6923ac41e8b6d4f9@mail.gmail.com>
- In-Reply-To
- <200909272001.48180.robin.rosenberg.lists@dewire.com>
On Sun, Sep 27, 2009 at 8:01 PM, Robin Rosenberg <robin.rosenberg.lists@dewire.com> wrote:
Show 7 quoted lines
> söndag 27 september 2009 14:24:32 skrev Anteru <newsgroups@catchall.shelter13.net>: >> Mercurial's revision number system: With git, I get an SHA1 hash for >> every commit, but it's not possible to see whether Hash1 is newer than >> Hash2, while Mecurial also adds a running number to each commit. What's > > But those numbers cannot be communicated since they are local to your > clone.
You can use git-describe, which will look for the latest tag, and make a combo of latest tag, commits since the tag, short form of sha1. So you get "v1.6.3-33-g1234" - 33 commits after 1.6.3. Works very well to integrate in versioning. The git project itself uses it in the Makefile to set the versions, same as the kernel folk do -- I use it to version even RPM/DEBs.
hth,
m
-- martin.langhoff@gmail.com martin@laptop.org -- School Server Architect - ask interesting questions - don't get distracted with shiny stuff - working code first - http://wiki.laptop.org/go/User:Martinlanghoff