|
Message
From: Jeff Carr<basilarchia@g...>
Date: Mon Apr 17 18:21:13 CEST 2006
Subject: [oc]SVN - resolution
On 04/14/2006 09:13 AM, Damjan Lampret wrote:
> I'll ask the web admin to start with integration of SVN. I don't promise
> anything. But the plan is to go slowly and implement SVN as an option to
> the CVS, so both would be available. This will require changes to the
> many parts of the web site, so it will take 2 months or so.
Please rethink this, use git!
While SVN is certainly nice in that it provides a web interface, so does
git. However, SVN is terribly slow -- it's insanely CPU intensive. I
don't think it's going to work well for a big project like this. If you
are going to upgrade from cvs, upgrade to git. I see this as the trend.
The Linux kernel developers have developed git over the last year:
(http://kernel.org/git/). SVN was suggested, but it didn't win approval
so git was written from scratch.
If you are really going to follow a migration path to a newer SCM, this
is a better path. X windows and Wine are examples of large free software
projects that have gone in this direction.
The important advantages:
1) git is cpu efficient
2) git is bandwidth efficient
3) git is smarter about offline development
3 is important/useful here. git makes a mirror (via rsync if you wish)
of the repository on the server on to your local machine. This is smart!
You have an exact mirror of the history, etc. Unlike CVS and SVN where
what the server stores has no correlation to what you checkout.
SVN is better than CVS, but it is still pale when put against git. If
opencores is going to move forward, use git.
Enjoy,
Jeff
|
 |
Browse
