The chronicles of SQL Relay, Rudiments, and other firstworks technologies

...and general adventures in Software Development, IT, and computing.

Friday, December 8, 2017

Firstworks GIT Migration

I'm fairly well known, among friends at least, for liking to get every last mile out of vehicles, equipment, gear, and just about everything else. Every last mile. The night before last, I discovered that I had gotten every last mile out of Sourceforge's CVS service.

I'd made a couple of changes, run a commit, and bam!

###############################################################################
CVS commits are NOW DISABLED! This was first announced on October 5th, 2017:
https://sourceforge.net/blog/decommissioning-cvs-for-commits/
This project's data may be converted over to a new SCM. Use the project's
menu to see where the current code is kept:
https://sourceforge.net/projects/PROJECT_NAME/
To access the CVS data, either use a pserver checkout or an rsync backup.
In the following commands, replace PROJ with the project name and MOD with
the module name:
cvs -z3 -d:pserver:a.cvs.sourceforge.net:/cvsroot/PROJ co -P MOD
rsync -aiv a.cvs.sourceforge.net::cvsroot/PROJ/ /dest/dir/
Conversion instructions for svn and git are available here:
https://sourceforge.net/p/forge/documentation/CVS/
###############################################################################

Ha!

Well, I wasn't too upset. It's not like I didn't see it coming. A few years back I tried to get git working on all the old platforms in the compile farm. That ultimately failed, but I worked out a better solution last month and I've been trying, off and on to get my CVS repos converted to GIT ever since.

Good thing! I needed the experience of all of the failed attempts, and some advice from a buddy of mine to finally get it working today.

So, as of today, all Firstworks projects have been migrated from Sourceforge-hosted CVS to Sourceforge-hosted GIT.