Hi everyone, Our Mediboard project source code has been relocated from an SVN sourceforge repository to another repository. Should I just add this repo and remove the former one, probably resulting in ... [More] a reparsing of the whole 30k+ revisions project, or is there a way to relocate (as of svn relocate command) to prevent that? Cheers, [Less]

Hi guys, It looks like Mediboard project code hasn't been parsed for more than 3 months now, yet the code is still accessible. Thanks for your help.

Yet it happens once again... I was wondering if I could somehow merge and import all 30+ old CVS modules into one SVN repository, to simplify Ohloh parsing job. In fact, those are the old repos ... [More] used in Mediboard early age in 2004/2005, but they won't evolved ever again... Whereas the unique SVN repos is the one we actually use everyday. [Less]

I confirm, the job is done perfectly! There were no hurry though...

Hi Jason, There's something I don't get in your policy. When you say If a project has migrated repositories and did not backport their old history into the newer repository what is that supposed ... [More] to mean? How a project that has migrated its code repository could not backport code to the newer ? I'm probably missing something due to my english understanding of backport, sorry. Could you please rephrase this? My case is simple: I administrate the Mediboard project. We have migrated from a CVS to a SVN repository for well known reasons, with the exact same code. Shouldn't I be enlisting the older CVS rep on Ohloh to reflect the real Mediboard history? Thanks in advance for your clues. [Less]