Thanks a lot! We've merged quite a lot of new code recently so I thought it would be nice to have the Ohloh statistics reflect this. Jakub

Hi, I am just repeating my old idea, which probably got lost already. But because it seems to have been accepted positively, I am posting it again. It would be useful if it was possible to declare ... [More] one enlistment as a continuation of another one. Imagine a project which switched from one VCS to another, but did not import the old history into the new VCS. Ohloh will then count LOC twice - once for the enlistment representing the old repo and once for the enlistment representing the new repo. Cheers, Jakub [Less]

Uff, that was a mistake :-)

Hi Robin, I've figured out how to bypass that limitation - we have dumped the Subversion repository as of the revision before which we moved /boot/trunk, /kernel/trunk and /uspace/trunk under /trunk ... [More] and imported it into HelenOS-historic repository. Then we simply had ohloh to import this historic repo. I already see all the developers who were missing due to the limitation. However, it seems like it is taking already too long for ohloh.net to update the report for HelenOS. Moreover, even though I see the older developers, I still don't see the older history. Couldn't you push it a little bit and verify that HelenOS is not excluded from report updates? Thanks, Jakub [Less]