[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [glob2-devel] changing glob2 cvs-repository to mercurial!
From: |
Kai Antweiler |
Subject: |
Re: [glob2-devel] changing glob2 cvs-repository to mercurial! |
Date: |
Fri, 02 Feb 2007 13:54:51 +0100 |
User-agent: |
Gnus/5.1007 (Gnus v5.10.7) XEmacs/21.4.20 (linux) |
> I agree we should change our version control system, but why mercurial in
> particular?
I think they are all good. I skipped mercurial initially, because it
was in debian testing but not in stable. I thought that the reason
for debian might be that mercurial is not that big a project or flawed.
But I erred. Mercurial is very young (2005) and some big projects
use it (as a result of selection procedures).
But darcs and bazaar-ng and monotone have their own advantages
and disadvantages.
When Matthew and Joey wrote that they already use mercurial,
I made it my favorite and started looking into it. It is extremely
well documented. And the documentation seems to be up to date.
So I tried it and I liked it.
> It doesn't seems to be famous (I've been looking into such
> systems lately and never heard about mercurial), even if some big projects
> use it.
Well it is young.
> How does it compare, for instance, to darcs
> (http://abridgegame.org/darcs/ that has a very solid math
> background)?
I haven't read about the that mathematical background.
Were did you find it?
I don't know specifically. Most reviews are old.
What I can say is:
* monotone nowadays uses only netsync protocol for networking.
No http support. Big minus.
* bazaar has a confusing name.
On some distros bazaar means the old project on some the new.
Big minus.
darcs:
pros:
innovative
best merging
easy to use
good documentation
bad repository history
cons:
very slow
bad error messages
small development crew, due to it's being written in haskel
mercurial:
pros:
extremely good documentation
easy to use
fast
big projects choose it
rapid development and up to date documentation
(you will know the new features and be able to use them.)
cons:
there were some, but I don't remember.
monotone:
pros:
every feature that causes problems will be eliminated
written in c++
cons:
fewer features (especially pull and push are limited now)
bazaar-ng:
pros:
financial backing from canonical
rapid development
cons:
confusions with the name. (Some distributions use the name "bazaar" for
the old project.)
At least this is what I can remember.
--
Kai Antweiler