about 1 year ago
Hello. I'm the manager for http://www.ohloh.net/projects/origami and I noticed that in the last update some commits are missing. In particular I miss those in which I deleted trunk/ and recreated it with a new and updated version of my software, greatly different from the previous (i.e.: no JavaScript at all).
Should I wait until the next update and see or is it necessary to manually reset the stats?
about 1 year ago
I may be experiencing a similar issue; I did something similar today and I'm missing all but the most recent commit. My situation is for http://www.ohloh.net/projects/libdmtx, for which I added an enlistment today with history going back to 2006. However it only shows one commit. That one commit is from today, in which I moved all my files and directories from "/" to "/trunk" in Subversion.
about 1 year ago
Hello again. My project seems to have been updated some minutes ago but still it's missing some commits and still it's listing wrong informations about the code.
about 1 year ago
Our Subversion importer is not able to follow directory renames or branches.
If you rename or move a directory, all of the prior history of that folder will be lost to Ohloh, and we will only see activity after the move.
If you pass the --stop-on-copy flag to svn log, you'll see your history the way Ohloh sees it.
about 1 year ago
Hi Robin, thanks for your quick response. Are there any plans to give your Subversion importer the ability to see history before directory moves?
Ironically the only reason I spent so much effort merging my SVN history was because I got tired of Ohloh telling me that my project had a "Short source control history".
Instead, now it just looks like I wrote 17,000 lines of code yesterday. :)
about 1 year ago
Hi Mike,
I'm sorry your source control struggles went unrewarded here :-(. I've gotten enough experience at these things lately to appreciate what a pain it can be.
I've wanted to fix the branching/renaming limitation for a very long time, but it turns out to be harder than it first appears. We simply haven't had the development resources to work on it, but I'm hopeful that down the road we'll have the chance to revisit this.
about 1 year ago
My problem is a bit different from Mike's. I removed all the files under trunk/ (and even removed trunk/ itself) and then recreated. So, to my understanding, it should be seeing a removal of files and a creation of new files.
Even better: the new files have different names that the old ones.
Does this go under the same behaviour?
about 1 year ago
Yes -- your specifics are different, but the root cause is the same.
Our basic problem is that when a directory is created, we aren't able to determine whether that directory was copied or moved from somewhere else... or whether another directory with the same name used to exist in the same place. When a directory gets created, we simply assume that there's no history before that.