Source control for all dmd source (Git propaganda =)

[Daniel Keep]

Jérôme M. Berger wrote:
> Leandro Lucarella wrote:
>> Anyways, my point was, putting DMDFE in a SCM would be great, even when
>> it's svn. For me the ideal would be Git, Mercurial or other distributed
>> SCM would be nice, but even svn is better than we have now =)
>>
>     Oh, I agree. However, IMO git is a poor choice. Mercurial, Bazaar or
> svn would be better.

After having used both git and svn, I'll have to VERY strongly disagree
with that last part.  I'd imagine that *any* half-way sane DVCS would be
better than svn.

As for the others, you don't provide any objective reasons for WHY
they're better than git.

>     For some interesting reading:
> 
> - Here are the reasons that pushed Python to use Mercurial (includes the
> reasons for the change from centralized to distributed SCM and the
> reasons for choosing Mercurial): http://www.python.org/dev/peps/pep-0374/

The weakness of Git's support for Windows relative to the others is
probably a valid point; I haven't used the other two.

It's worth noting, however, that I *do* use Git in both Windows and
Linux and I've only felt disadvantaged on Windows in one specific case:
the Windows build lacks svn integration. [1]

Another reason was "it's not Python," which is obviously irrelevant in
this case.

The only other reason was popularity.  The table doesn't really specify
WHY the others were more popular.  This could be either that mercurial
is much easier to use, or the majority of Python devs prefer typing two
characters instead of three.  :P

> - Here's the same for Mozilla:
> http://weblogs.mozillazine.org/preed/2007/04/version_control_system_shootou_1.html

That's over three years old and the only reason stated is that it is
"lacking Win32 support" which is obviously no longer true.


[1] Apparently this is because the svn integration depends on the perl
svn bindings, and no one can get both perl AND perl-svn compiling with msys.