Hello List,
I just found this weblog about this subject:
http://blogs.oracle.com/duffblog/2007/05/07#a411
By the way, I vote for Subversion although Netbeans support isn't as
good as Eclipse one.
I worked with both Systems and Subversion more intuitive for me.
But maybe I'm getting a more
Thanks Sunburned. I read the article linked to in Malte's post. I can see
where Subversion's atomic commit would be important in some environments,
but with the kind of service that I get from SourceForge, I would never get
anything done if I had to start over each time I got an error.
I use CVS for work, which is enough to make me a big subversion fan
:-) Atomic commits are the big thing I like, but I'm also a big of
sym-link support. That one isn't a big issue with this code base, I
imagine, but I like it anyways...
-Craig
the same, as michael says, holds for me.
I dont have any feelings against subversion, but why switching to
another systems if everything works fine.
And you may remember that i send a link around where somebody did
compare svn and cvs, and according to this person there is no clear
advantage
Stefan,
How is you thesis going? I hope well.
You wrote: And you may remember that i send a link around where somebody
did
compare svn and cvs, and according to this person there is no clear
advantage for either system.
I think there is some small advantages to SVN, at least on the
While we're talking about upgrading things...I thought I would again mention
the idea of moving our code repository over to Subversion. I have been using
Subversion at the SurveyOS project for a while, and it really has some
advantages over CVS. (You don't need to put in a SourceForge service
Are any of the other developers using Subversion? Are there still
strong feelings against the migration?
No opinion, just like the most simple solution. I prefer having time to
improve jump than to configure cvs/svn access :-) .
The Sunburned Surveyor
