Forum Posts

Hello, I am wondering how repository moves and copy work. If a project was in a directory A on SVN and was then moved (with svn move) or copied (branched with svn copy) to a directory B. The most ... [More] recent repository for the project will be svn:..../B and apparently ohloh stops searching the code history at the "copied from..." step in the SVN history. In a same way, for some project, with SVN, the directory was first C, but then, because of history branching (and bad initial organisation), the project was divided in: C/trunk C/tag1 C/tag2 ... ohloh will only enlist the trunk and would not get the whole history of the project. What should we do to link it with "older" history, just add a new enlistment? but if it's a fork, it's only needed to link it to the history once and not to update the enlistment regularly... There could be an option in the code enlistment to say: this code base was a jump from this history. This way, it will register the whole history (and all contributors) to the project and not just the history from the copy/move. [Less]

I am sorry for the double post earlier, there was a problem with the site just when I posted I think. The git repositories seems to be catching up and the sourceforge project was updated correctly ... [More] apparently. That's cool, thank you. I submitted new projects from zone.spip.org and they were fetched without problems, but the one I submitted last week (and SPIP) are still marked as failed. [Less]

Andy/Robin, Our SVN root should now be fixed. We applied pretty much the same technique as the Adium guys, except as it applies to a Sourceforge repo. Please give our enlistment another kick and ... [More] hopefully it should complete this time. I tested with version 1789 and had no problems. Thanks again for pointing out the problem in our repository as well as to the fix! It'll be nice to have our stats online again. Cheers! Sean [Less]

The user rank count has not been updated since September 15th.

We have a bunch of XML files in our repository that are tagged as "text/xml" with subversion, but have the ending ".hsi". Those aren't recognized as XML files. It would be nice if ohloh could use the mime-type in case of unknown file types.

Is there a parsing engine that I may be able to help configure for Fortran?

Ah, that makes perfect sense, thanks for the explanation. Maybe it would help to use one of the cvs mirrors ( see http://www.netbsd.org/mirrors/#anoncvs ) - some might have more bandwidth and/or less load than cvs.netbsd.org.

Are you still there, Andrew? Are you still getting email?

Ack! There appears to be some strange database problems with our posts right now, including deadlocks and timeouts. I've been investigating this, and I'll probably have to kill of all notifications ... [More] for now. Thanks for the heads-up, and sorry about all the mail, Robin [Less]

+1 That would be great! :)