A helpful post I’ve since lost pointed me to ‘svn propdel svn:eol-style’. rpt files imported as text files, and thus had inconsistent line endings. Once converted, I did some litmus tests: check the files out, are they the same as the ones I’m using for live development? Just about without fail, the crystal reports. I lost a few fingernails, but the data was gorgeous. Just when I was to give up, it’d pick right back up with the next step. The conversion froze at various points with very undescriptive details about what I thought it wasn’t doing. I just pointed cvs2svn to the project folder, and pushed go. Splitting it out this way was actually quite easy. Since I work with various clients and various projects, and I didn’t want to flood the repository version number for unrelated content, I decided one repository per project. I also put svn, python, and cvs2svn in my PATH. Though the recipie was long, it was detailed, and effective.) I noted that since I was using CVSNT, I was in “uncharted territory”. Next, a few more downloads: cvs2svn, python, the subversion python bindings, WinMerge, the kitchen sink, and some boots. I installed CVSNT, TortoiseCVS, copied my repository onto the VMware session, and made sure it was good. Ok, armed with knowledge from front to back, I was ready to tackle the conversion. I think my wife was not overly thrilled when I brought it to bed. But TortoiseSVN even played nicely with TortoiseCVS’s hog of the available Windows Icon overlays. Ok, versioning folders was a bit weird at first.

It was a natural fit from using CVSNT and TortoiseCVS. I installed Subversion, the Windows Service wrapper, and TortoiseSVN.

Next up, I fired up VMware, and created a “subversion sandbox”. It was by far the best move I could’ve chosen. Ok, time to make the move.įirst step, I signed up to co-present Intro to Subversion at the Desert Code Camp – something about buring the ships in the harbor. In passing, while discussing something else, he mentioned that anyone still using CVS should get onto SVN. I’ve always wanted to test out Subversion – see how green the grass was on the other side of the fence.

I’ve saved my bacon more than once with it in Windows when I got down a coded road that just didn’t work out. I’ve scripted it on Unix with automated build and deploy scenarios.

It’s a great (and free) way to keep my source code in check. I’ve used CVSNT and TortoiseCVS for ages.

Svn winmerge