Phil Dawes' Stuff - Latest Comments in BazaarNG and Mercurial and Git

Re: BazaarNG and Mercurial and Git

Seth — Wed, 12 Mar 2008 16:31:18 -0000

I'm stuck to using AIX 5.3 at work.

Of Darcs, Git, Cogito and the lot, Bzr (1.2 at the moment) is the only thing that I can even get working (and I'm very used to tinkering for days with configure to get things ironed out).

Much to my surprise, Python 2.5.2 was relatively straight-forward on AIX. (event though IBM's AIX Linux Toolkit offers 2.3* only!) That gives me Bazaar pretty much for free.

Bzr has come a long way: it doesn't feel sluggish to me, has awesome integration with subversion (our central repo).

GIT was absolutely horrible to try to compile/build/install. I sort of got it working, (basically doing all msgfmt and install steps manually) but then it started borking at runtime. Not a happy git :)

Re: BazaarNG and Mercurial and Git

pradeep — Tue, 12 Jun 2007 05:04:21 -0000

Hg is faster than bzr but git is much faster than Hg.
Atleast on my Pentium D machine it is.

Has nice branches feature in the same directory which is really really helpful.

Tags act as checkpointing snapshots for me.

I can create a new branch from a working tag or overwrite a messed up branch :-).

indeed there are too many commands but essential ones are very simple to use.

In end IMHO git is way to go if you are choosing to manage your src on a POSIX complaint filesystem.

If you prefer windows ,i ll suggest Hg.

thanks

Re: BazaarNG and Mercurial and Git

Bryan O'Sullivan — Tue, 20 Jun 2006 11:36:27 -0000

Coming very late to the game, but Mercurial is still a lot faster than bzr, and handles in-repo branching, a la git.

Re: BazaarNG and Mercurial and Git

James Henstridge — Thu, 27 Apr 2006 10:32:07 -0000

You might want to check out bzr 0.8 when it comes out (should be within a week), as it addresses a number of the issues you bring up.

There is a new branch format that will improve network performance.

There is a new repository concept that allows you to share the version control information for multiple branches in a shared location (a parent directory). If your branches are related, this will save a lot of space. You can also have branches without a working tree (i.e. only version control data).

And while bzr is backed by Canonical, there is a fair number of external contributors (just check the revision history).