It's been a couple weeks. So doing a quick scoring (using
http://wiki.metalforge.net/doku.php/user:rednaxela:scmtable as the reference):
CVS SVN Hg BZR DARCS
Key Requirements (7)7 7 6¹ 7 6¹
Top Features (6)3 3
Mark Wedel wrote:
Mercurial: If a good hosting service is available, this may be the best
option.
But hosting here is tricky - commits, at current time, seem to need ssh
access
(may change to https in the future).
One note on this, as of Mercurial 0.9.1, you can push via http as
Mark Wedel wrote:
Alex Schultz wrote:
Mark Wedel wrote:
Mercurial: If a good hosting service is available, this may be the best
option.
But hosting here is tricky - commits, at current time, seem to need ssh
access
(may change to https in the future).
One note
Mark Wedel wrote:
It's been a couple weeks. So doing a quick scoring (using
http://wiki.metalforge.net/doku.php/user:rednaxela:scmtable as the reference):
CVS SVN Hg BZR DARCS
Key Requirements (7) 7 7 6¹ 7 6¹
Top Features (6)
Darcs: Has the same lack of hosting as mercurial, and otherwise isn't really
better in any regard, so don't see a very compelling reason to look into
darcs.
alioth.debian.org hosts several projects using darcs and they're quite
happy to host non-debian projects. This has the disadvantage of
On Tue, 22 Aug 2006 10:28:24 +0200, Tchize [EMAIL PROTECTED] wrote:
I did not follow this thread, but am curious on this point on the wiki
page. It's stated 'good branch handling' on CVS and SVN as no. Am sorry
to raise it now, but i have been using branching on CVS at work for a
while and
Raphaël Quinet wrote:
As a GIMP developer, I have been using
CVS branches extensively: we always maintain HEAD together with at
least one stable branche, while several experimental features are
developed in their own branches, such as the recent Google Summer of
Code projects. We also
7 matches
Mail list logo
