Re: [Perl-workflow-devel] Migrating from CVS to SVN as SCM
Brought to you by:
jonasbn
From: Jonas B. N. <jo...@gm...> - 2007-01-25 09:58:48
|
Ok, So we migrate to SVN. I am currently in the process of organizing the Nordic Perl Workshop, so I am quite busy when not working, but I will attempt to line up everything and write a simple, and then I will notify the list again with the plan. Then we can set a date and execute the plan. This might seem overly strutured, but I need this in order to schedule it with my other activities. jonasbn On 25/01/2007, at 9.55, Alexander Klink wrote: > Hi Jonas, > > On Thu, Jan 25, 2007 at 09:43:31AM +0100, Martin Bartosch wrote: >> sorry for the late answer, I was quite busy... > same here (same project :-) ... > >> A friend did this on SF and as far as I remember it went smoothly and >> without any problems. SVN has many advantages, and I would appreciate >> to have a SVN repository instead of CVS. > I fully agree. Atomic revisions for the whole set of files instead > of for each file individually and the ability to use it even behind > really restrictive firewalls are the key killer features for me. > > Regards, > Alex > -- > Dipl.-Math. Alexander Klink | IT-Security Engineer > ak-...@cy... | working @ urn:oid:1.3.6.1.4.1.11417 > > ---------------------------------------------------------------------- > --- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to > share your > opinions on IT & business topics through brief surveys - and earn cash > http://www.techsay.com/default.php? > page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > Perl-workflow-devel mailing list > Per...@li... > https://lists.sourceforge.net/lists/listinfo/perl-workflow-devel |