On Wed, 2004-10-06 at 09:19 +0200, Jan Kiszka wrote: > Hi all, > > since my first contact with subversion, I'm quite enthusiastic about the > new features this versioning system provides (e.g. fast offline diff'ing > of local modifications). However, migrating RTnet to svn isn't something > we may do over night. Therefore, I would first like to collect any > comments or objections about the following plan: > > o freeze the CVS, grab its backup from SourceForge, and convert the > tree to subversion (already tried this successfully with yesterdays > version) > o create a new project for RTnet at berlios.de > o import the subversion tree to berlios > o create and add accounts for all developers at berlios > > The mailing list, the file releases etc. will remain at SourceForge. > Maybe (or likely) they will offer svn services some day as well, and we > can migrate back to have everything at one place again. > > What do you think? Has anyone already production experiences with svn? > Any traps and pitfalls? >
The only pitfall I found is that you have to watch out what you check out. When you don't you will get all tags/branches local, and that will eat a lot of diskspace locally. But the SVN handbook has some good examples on how to do the branching (the CVS to SVN tool will create a lot of branches and tags, that might need some cleaning). - Erwin > Jan ------------------------------------------------------- This SF.net email is sponsored by: IT Product Guide on ITManagersJournal Use IT products in your business? Tell us what you think of them. Give us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more http://productguide.itmanagersjournal.com/guidepromo.tmpl _______________________________________________ RTnet-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/rtnet-users
