Forum Posts

In that case I'll just delete the CVS enlistment; there weren't many changes between the initial CVS commit and the switch to SVN. I do think limiting an enlistment by date or revision number would ... [More] be handy though, to handle things like forks that don't import the pre-fork history explicitly. [Less]

What command are you using that's giving you an error? I just checked out revision 247 and used "update -r###" to update manually past revision 269 (where the issue was corrected) and none of the ... [More] update commands gave an error. By "administrative tools", I assume you're referring to svndump, svnload, and svndumpfilter. I'm happy to look into it if you know what the specific commands or arguments are, but so far I haven't found anything obvious. I'm not sure that's a great fix though. The line endings were corrected in rev 269, and if I changerev 248, 269 would be redundant. Removing it would change all of the later revision numbers (invalidating those in commit messages), and, I assume, would require all users to re-checkout the project. Even if I'm comfortable with that change, which could potentially mess up the rest of the history, other, larger projects probably won't be, so it seems like something you'll need to deal with eventually, one way or the other. [Less]

The tporpheus project switched from CVS to SVN for source control but rather than using cvs2svn they just imported a copy of the current source code and left the CVS repository around in case anyone ... [More] needed it. I added the SVN repository to the enlistments, but now it's showing twice as much source code as there should be. Is there a way to adjust things so it only uses the CVS repository up to a specific date? [Less]

Shows it failed counting lines of source code. Also, I don't remember how long ago I added the exclusions, but it was at least a month ago, and it shows "All files included" on the Enlistments page. https://www.ohloh.net/p/tpabbrevia/enlistments