Hi, Am 14.02.2011 10:00, schrieb IOhannes m zmoelnig: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On 2011-02-01 15:11, Burkhard Plaum wrote: >> >> I'll try to look into this once sourceforge CVS is up again...
First of all thanks for reminding me about the SSE crash, I'll look into that now. > btw, reading > https://sourceforge.net/blog/sourceforge-attack-full-report/, it seems > that sf has plans to turn off CVS on the long run: > "We are also considering the end-of-life of the CVS service and hope to > have user support in migrating CVS users to Subversion in coming months. > Subversion generally provides parity to CVS commands, and many of our > users have made this transition successfully in the past. > > - From SVN, projects can move to Git if desired." > > i don't know about your (burkhard's) feeling about other VCS, but CVS > seems indeed a bit outdated by now. > i remember transition from CVS to SVN to be very painless (unlike > transition from SVN to git, which involved learning), though the memory > is slowly fading away, as this has been some years now. > otoh, i also remember switching back from SVN/git to CVS (mainly to > generate a simple, multi-file diffs for...gmerlin) to be a real pain. > > anyhow, if switching to one of these VCS i would recommend: > > - - to use git, if you intend to keep gmerlin evolving > e.g. i really love the possibility to do offline commits (e.g. working > at home, on the train,...) > branching/merging is really a piece of cake, e.g. adding new features ca > first be developed/tested on a separate branch and then simply be merged > into the stable main-line (that's all possible with CVS as well; but git > helps a lot) > > - - to use SVN, if future development does not need any of the above. > e.g. if you only intend to fix the odd bug now and then, then it's > probably an overkill to use git. if you are always online when > developing, then you don't need offline commits. > most important: if you never worked with git, then it will take some > time to get used to it. > > masdr > IOhannes A CVS -> SVN transition would be more than welcome. If there is a volunteer for this, I can give the necessary permissions. If would be important that the history is preserved though. My opinion about git is quite weak. I understand it's state-of-the-art VCS, but my feeling is that it makes sense only if there are more than one core developers. In my opinion, patches sent to the mailing list and applied to CVS/SVN worked perfectly in the past. But I'm open to other opinions of course. And since the transition would be cvs -> svn -> git, the svn transition could be done right away. Burkhard ------------------------------------------------------------------------------ The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb _______________________________________________ Gmerlin-general mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/gmerlin-general
