Results 10 - 20 of 54.

587 VIEWS

ohloh doesn't completely understand svn completely. Does "svn log --stop-on-copy" show the commits you are concerned about? If not this is your problem. Sometimes errors (particularly character ... [More] encoding errors) cause bugs like this. Can you view the svn logs around the time of the last reversion that made it into ohloh? An error in those logs can be the reason. If the cut-off point is a point of conversion, a simple solution is to point ohloh at a copy of the old repository as a new enlistment. [Less]

330 VIEWS

If you want asp recognised, head over to link and add it. cheers stuart

364 VIEWS

This is a known problem, sorry

253 VIEWS

You need to go to http://www.ohloh.net/projects/9483/enlistments and check that the git repos listed there are the ones currently in use. If they are the ones currently in use then complain again. ... [More] If they're not the ones currently in use, add new ones [Less]

319 VIEWS

ohloh doesn't parse forth because ohcount doesn't parse it yet. Go to http://labs.ohloh.net/ohcount to lend a hand getting a parser written.

565 VIEWS

The problem with a scheme like this is that every project has a different format for these and it would be really hard to do things automatically.

392 VIEWS

It's tempting to suggest that project RSS feeds could be generated through the API with a little XSLT, but I won't look into that if there are performance issues...

392 VIEWS

"Changed bestanalysisid to 221575" by "The Ohloh Hamster" means that the ohloh system (i.e. the hamster) re-analysed the code and the new code has id 221575. There is no particular significance to the ... [More] id, except that it's an index into the underlying database tables. [Less]

342 VIEWS

The more I think about this problem (and it's an issue for my greenstone project too), the more i think there might be a hack that users can do. Basically the user sets up a mirror of the repo ... [More] immediately before the move and adds it as a new enlistment. Once it's processed it's deleted (it's only history, so it never needs updating). Do you have a feel for whether that you work Robin? or would it break other stuff? [Less]

342 VIEWS

It looks like the update failed, you'll have to get someone from ohloh to look at it: ttp://www.ohloh.net/projects/OpenGroupware/enlistments