Guido Tack wrote:
Hi Boriss.
Kevin was looking at Sourceforge and Savannah sometime in the past, but
I just remember that his conclusion was that we were going to lose the
history of CVS. I don't know if that is the case if we first port the
repository to SVN, and then we put it at Sourceforge. Savannah does not
support SVN yet. I haven't used SVN very much yet, but according to the
basic advantages that it presents, I also think we should switch to that.
Sourceforge supports importing complete svn dumps. It is possible to convert
the Mozart CVS to svn, including complete history (we've done that for
Gecode), and then import the svn in sourceforge.
excellent, so we can keep the whole history of development. Did you use
the tool cvs2svn?
I can tell you from our experience with Gecode that svn is so much better
than CVS. E.g. some weeks ago we had to move complete directories around,
which is a nightmare with CVS and worked perfectly with svn. Updating my
local copy that contained changes to files that were moved in the
repository worked perfectly.
yeap, moving files or renaming them is one of the advantages, but also
the fact that diff is done per byte and not per line makes patches lot
more efficient. What I also like is that network traffic is also more
efficient since it only sends diffs of the files, and not the whole file
each time. Having a revision number for the whole project instead of
file independent numbers is very convenient as well.
cheers,
Boriss
Cheers,
Guido
_________________________________________________________________________________
mozart-hackers mailing list [email protected]
http://www.mozart-oz.org/mailman/listinfo/mozart-hackers
