On Wed, 13 Jun 2007, Felipe Balbi wrote: >On 6/13/07, Marc Moreau <[EMAIL PROTECTED]> wrote: >> I have played with SVN, and did a moderate study of it back in 1.3.2. >> >> With Geda, there should be no problem using SVN for version control. Most >> (all?) geda files are text and SVN is optimized for that. > >You really like SVN?? you should try git... SVN is not a source code >management system... it's just to get us bored :-p >
I am not against using git, but I need to protect SVN here. One needs to see both the adventages and the drawbacks. With git, I will need to worry about disk space, because checking out a repository will download and store much more than an SVN (or CVS) client. If I'm an active developer, it may be a good idea, having my own history, but if I'm only an user interested in the latest revision, this may be a pain. Especially if I don't have 160 gig disks. Of course, with newer git versions there may be a way to get the latest release only using extra command line arguments, but an "svn co svn://something.org/project/trunk" may be simpler for users than a long command line. I am not sure (yet) how git works, does the same happen with updates? Can I use an "svn up" type command and only have the latest revision and no local copy of the whole history? The other important point is the distributed vs. server-client approach. Everyone having his own repository is really nice because more develoeprs can start experimenting with the code and they can share their modifications easier. However, the "boring" server-client setup with it's centralized approach can send an email or irc message on any commit to a mailing list so developers see what other developers are working on in a branch. The repository is usually hosted on a high bandwith server so everyone can get the files fast. The serve may have a stable network connection and high uptime. Comparing this to having to connect a random developers home computer behind an adsl fo a specific branch has drawbacks. Or if the developer pushes (?) his branch to a central server, we are back at client-server approach. Or does git have a trick for this as well? People usually say that svn is centralized and you can not work offline for long because you can't save little commits. Of course, with vanilla svn it's true. However, there are ways to change this, for example svk, so one can have a distributed svn. Finally, I think it's a good idea to keep read-only CVS mirror if the project moves to git (or anything else). Igor2 _______________________________________________ geda-dev mailing list [email protected] http://www.seul.org/cgi-bin/mailman/listinfo/geda-dev
