After moving a folder in the svn repository and changing the enlistment accordingly, the history of the project is missing in ohloh.
All revisions are still present in svn. How do I get the ohloh code history back?
After moving a folder in the svn repository and changing the enlistment accordingly, the history of the project is missing in ohloh.
All revisions are still present in svn. How do I get the ohloh code history back?
Hi m_m,
Ohloh only shows commits that appear in the svn log for the specific URL you provide.
In this case, svn log https://pyspread.svn.sourceforge.net/svnroot/pyspread/trunk only shows commits as far back as revision 228.
If a directory is copied or renamed, in many cases Ohloh is able to follow this change. However, if you look at the log for revision 228, you can see that there is no prior history indicated. The /trunk directory is simply created from scratch in revision 288, and no link back to older history is provided.
To obtain all of the older history on Ohloh, there needs to be a branch that exists today that includes a continuous, unbroken log all the way back to the older history. Is there an URL in the project today that has a log going all the way back?
Hi Robin,
I just moved the files (via svn move) down from https://pyspread.svn.sourceforge.net/svnroot/pyspread/
Therefore, a complete log file should exist in the parent directory of trunk. However, when I enter the url without "trunk/", ohloh fetches the trunk directory automatically.
Hi m_m,
Yes, unfortunately, it is difficult to convince Ohloh to track the root URL for a Subversion repository.
That's because Ohloh tries very hard to avoid importing the branches and tags directories. Because these directories can contain many duplicate copies of the code, including them can result in severe over-counting of the source code, by many orders of magnitude.
If your project does not contain any branches or tags, and you promise that your project will never have them, I can enlist the root directory manually. Otherwise, we have to accept the limitation that Ohloh must avoid using URLs that include branches and tags.
Hi Robin,
Since I moved to trunk because of new branches, I cannot promise that. Could you exclude the branches and tags directories instead of restricting everything to trunk?
Anyways, I would love seeing doublet file exclusion from code analysis :-)
Thanks for your support.
We get a lot of requests to exclude directories. This isn't something Ohloh can do yet, but it is high on the list for possible new features. Stay tuned.