One of the standard arguments when choosing distributed source control
systems is the use of GIT. One of the Fedora guys had some choice words:
The most important factor is that the learning curve for Git is a joke. Many
of us whom have never used it before tried to do very simple tasks and ran
into nothing bur problems and non-intuitive actions. Bringing these up to
other git users or git maintainers and they just make you feel like your an
idiot for not knowing the special -foo -bar -baz secret options to make git
do what you actually want. The UI is a nightmare, and even replacements like
cogito are of no real help. We wanted the SCM to be simple and easy to use,
mercurial provides that.
The fact that it was in python, and not a bazillion shell files or C apps is
also a deciding factor. Red Hat / Fedora is a big user of python and we have
a lot of in house knowledge. We felt confident in being able to debug /
extend / enhance / contribute to the SCM should it be necessary. We felt
that the mercurial upstream was far more receptive to changes and addressing
needs than the git upstream.
Also it seemed easier to get ssh and http mercurial setup than git.
We get a lot of git pressure internally to, but mostly its because "I use git
for kernel, or freedesktop.org, and I fear change, so I'm going to scream and
yell to use git instead of anything else.'
-- Jesse Keating Release Engineer: Fedora
-a
--
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
