Forum Posts

Hi Robin, Thanks very much for your reply. I am looking forward to these improvements! Cheers, Benoit

Hi, First, thanks for Ohloh. It's a great project. Ohloh currently doesn't play well at all with projects that move from one location to another even within the same SVN repository. This is a very ... [More] common case, for example a KDE project will typically start in playground/ then move to kdereview/ then to some KDE/ module. Concrete requests: 1) please make it possible to add an enlistment covering a definite timespan in the past. For example, Ohloh currently warns people that Eigen (project 5393) has short revision control history because its current location was created only recently. But before that it existed at another location. So, I would like to add an enlistment for that old location that doesn't exist anymore. Ohloh doesn't accept that, complaining that the server didn't reply to a "svn info" request. The timespan needs to have not only a definite end but also a definite start: I don't want ohloh to analyze what happened before September 1, 2007 at that location (basically I had been trying to refactor another unmaintained project as a starting point for mine, and I gave up and restarted from scratch at that date. So any data from before Sep 1, 2007 would only serve to make the LOC curves very strange) 2) If that is feasible, consider (maybe optionally as it could break things) following the references of "svn cp" and "svn mv". I mean, when Ohloh find that an enlistment starts at a given date, this is not necessarily the date when that code was created from scratch, often if was copied/moved from somewhere else and SVN remembers that. Cheers, Benoit [Less]