Forums : Posts

Thanks Robin

Hi applegrew, Ohloh doesn't currently parse the source code looking for author information. We only use the source control log. It's possible that we might use this type of data in the future, but ... [More] it might be a while before we have time to implement this kind of feature. Also, manual authorship information tends to be pretty imprecise (and frequently out-of-date) when compared to diffs and commit logs. [Less]

Hi Jon, Kudos are only updated once per day. When you make a change to your account, sometimes it can take 24 hours for the changes to be reflected in your KudoRank.

Now it's fixed for me too... It needed 1,5 days, maybe I registered just exactly after the script had been run.

If shared repositories are supported, the same commit should be assigned to the same user id. See e.g. user okuji at GRUB and PUPA. For the PUPA vs. GRUB case, I would suggest to simply delete the ... [More] enlistment of the GRUB2 repo from PUPA and add a note to its summary. [Less]

Very peculiar. I am regenerating the report now to see if that fixes the issue.

Thanks. Looks like it's being picked up nicely now :)

Sounds fair. Subversion externals are currently handled the same way (intentionally or not), and from my experience these are often used to link to other projects, which I agree shouldn't be counted. ... [More] Plus, as you said, including them is easy if desired. So, good job, and again thanks for the fast response. [Less]

Ah, OK. I see -- yes, if you delete the last enlistment, Ohloh will hang on the the analysis until another enlistment comes along. If you don't have any other code to measure, yes, it will stick ... [More] around forever and requires manual cleaning. I'll take care of it. Thanks, Robin [Less]

Sorry AnMaster, I should have been a little more specific. There's very likely no problem in your repository; something just went wrong on our end. A project goes through a lot of steps before the ... [More] report appears on Ohloh. First we create a local mirror of the repository on our servers. Then we parse the log and store that in the our database. Finally, we count the lines of code to compute the reports. When something goes wrong, the cheapest thing for us to try is the last step only: the count. If that doesn't clear it up, we can back up one more step and try reimporting the log from our local mirror. Finally, if none of that cleans up the problem, it means that our local mirror is corrupted. Recreating our local mirror is painful because it can take a long time to re-download the entire project history to our servers. That's where we are now with SuperTux, It's taking a while, but the download is proceeding. It should take a couple more days. Robin [Less]