Hi Markus,
The explanation for this is rather long and complicated, so I'll hope you'll bear with me.
Ohloh only sees as much as the Subversion log contains for the URL you provide to us. If the Subversion log only goes back 5 days, then the Ohloh report only goes back 5 days.
Consequently, Ohloh does handle Subversion moves, but only moves of the exact root URL you provided to Ohloh. We do not follow the moves of the individual subdirectories.
For example, in this case, one of the the URLs given to Ohloh is http://svn.factority.org/repos/factority/factority/trunk/.
If you look at the log for this URL:
~$ svn log --verbose http://svn.factority.org/repos/factority/factority/trunk/
You will see that the log is very short, and it ends at revision r771 with a simple add:
------------------------------------------------------------------------
r771 | msheimhu | 2009-10-11 11:45:25 -0700 (Sun, 11 Oct 2009) | 1 line
Changed paths:
A /factority/trunk
Because it's a simple "add" event, Ohloh (correctly) doesn't attempt to find any previous history for this directory.
However, there are many proper moves for the individual subdirectories of this trunk. For example:
~$ svn log --verbose http://svn.factority.org/repos/factority/factority/trunk/factority-commons
In this case the Subversion log does indeed contain a proper move operation, and continues far back in history:
------------------------------------------------------------------------
r776 | msheimhu | 2009-10-11 11:47:17 -0700 (Sun, 11 Oct 2009) | 1 line
Changed paths:
D /factority/factority-commons
A /factority/trunk/factority-commons (from /factority/factority-commons:775)
So it boils down to the particular way this move was performed: rather than moving the root directory itself, a new root directory was created, and all of the desired subdirectories were moved into the new root. That's a case that Ohloh doesn't handle. A Subversion log of the new root does not go all the way back.
If you are dedicated, there is a workaround. You can remove the root /trunk directory from Ohloh, and replace it with individual enlistments to the individual subdirectories. You'll end up with a dozen or more enlistments, but in this case Ohloh will be able to successfully track the histories because each of these subdirectories will have a full Subversion log.
Let me know if I can answer any more questions,
Robin
