Boriss Mejias wrote:
>> 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?
Exactly that. It took some time to figure out the correct options, but we're
very happy with the result.
> 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.
Another very nice feature is that svn diff and svn status work without
contacting the network, so even when you don't have an internet connection,
you can check what you've changed.
One slight disadvantage is the speed over http, it's slower than CVS. This
however only matters for bigger transactions.
Cheers,
Guido
--
Guido Tack
Programming Systems Lab, Saarland University, Germany
http://www.ps.uni-sb.de/~tack
_________________________________________________________________________________
mozart-hackers mailing list
[email protected]
http://www.mozart-oz.org/mailman/listinfo/mozart-hackers
