Sorry for my late response to this issue - I was very busy during the last few weeks.
> If we decide to move to subversion, then I can enable subversion for > wxCode. Then, automatically the entire CVS repository will be imported > into SVN (CVS will remain untouched) with all its history. > Components of maintainers who want to use CVS should then be removed > from SVN and viceversa. > > To resume the situation, currently there are 2 developers voting pro (me > and cecilio), one voting against (john) and two undecided (otto?, > joseph?); is it right ? Until now I haven't used SVN, but word has it that it's a good versioning system. So maybe it's a good idea to switch to SVN. On the other hand I have no idea how complicated it will be to learn using new SVN tools. And I got along with CVS quite well. So add one more undecided. But I would strongly suggest to use only one versioning system. I find it quite inconvenient to use CVS _and_ SVN to get the whole of wxCode. Regards, Ulrich -- E-Mail privat: [EMAIL PROTECTED] E-Mail Studium: [EMAIL PROTECTED] World Wide Web: http://www.stud.fernuni-hagen.de/q1471341 ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _______________________________________________ wxCode-users mailing list wxCode-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wxcode-users
