[haiku-development] Re: Git/Hg: some speed tests

  • From: kallisti5 <kallisti5@xxxxxxxxxxx>
  • To: <haiku-development@xxxxxxxxxxxxx>
  • Date: Wed, 04 May 2011 11:11:22 -0500

On Wed, 4 May 2011 12:02:18 -0400, Ryan Leavengood wrote:
On Wed, May 4, 2011 at 11:50 AM, Oliver Tappe <zooey@xxxxxxxxxxxxxxx> wrote:
If someone has an idea how to create consistent revision IDs in Mercurial, please speak up, as otherwise, IMO, Mercurial won't do, no matter the vote. 

Even though I'm in favor of Git, the majority at this point seem to
prefer Mercurial. I wonder if we could just drop the global revision
ID concept and just deal with the SHA1 hashes for commits. Of course I 
feel the same on this regardless of whether we use Git or Mercurial.
We are changing tools and may have to change a few other aspects of
how we work. Saying Haiku revision 4d5b6789 is not as pretty as Haiku
r43215 but it isn't unworkable.
Looking at my previous email on this, a version number / hash combination 
seems to be a valid path.

[torvalds@g5 git]$ git describe parent
v1.0.4-14-g2414721

We could use the version tag to get a general idea on where we are and
use the hash on the end to get our exact commit location.

Both git and hg have this functionality:

[torvalds@g5 git]$ git describe parent
v1.0.4-14-g2414721
[otherguy@g5 hg]$ hg log -r . --template '{latesttag}-{latesttagdistance}-{node|short}\n' 


(although the git method is a little more graceful)

 Thanks!
  -- Alex

Other related posts:

  1. Home
  2. haiku-development
  3. Archive
  4. 05-2011