Re: switching to SVN ?

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I'm the Savannah Admin Marcus referred to. While SVN isn't the best  
(it has some of CVS's
limitations), its a lot better in many ways (atomic commits is the  
big one here), and its usually
only slow when used over WebDAV (http:// URLs). As it stands,  
monotone isn't written in a
way that would make it very easy tointegrate into any site like  
Savannah or GForge
(I tried to write a monotone plugin for GForge some time ago, and I  
wasn't able to adapt
monotone's idea of namespaces and such into an SCM without having to  
write a massive
amount of code).

As it stands, Savannah offically supports CVS, Git, and arch (the  
backend software,
Savane supports Subversion, but due to limitations, we decided not to  
offer Subversion
publicly at this time. If there is an exceptionally strong demand for  
another DVCS, assuming
it isn't too hard to intergrate, I might be able to add support to  
Savane and get to added to Savannah
(although will likely require more effort then its worth)
Michael

> My own experience with svn is that it is crappy enough in its own ways
> (mostly slow), and not enough better than CVS in any way, that it  
> is not
> worth the bother to switch from CVS.  That said, I will bow to the  
> majority
> preference of those who do frequent commits.  Myself, I would not  
> bother to
> switch any project from CVS to something else without going to a
> decentralized one.  I am no fan of git, though I do use it for  
> linux.  The
> decentralized thing I've found to be the least pain in the ass is  
> Monotone,
> but its use is not widespread.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (Darwin)

iD8DBQFGuk8xV/FBeJ6jsZQRAhbhAJ9RyeBSJVJwjm+/oRDqK/cFU3SEWwCdGkR4
lKNSbQX2kwS4gb+Xly0ADho=
=3ePQ
-----END PGP SIGNATURE-----