ColdSpring legacy CVS repository imported into GitHub

3 views
Skip to first unread message

Dennis Clark

unread,
Jun 20, 2010, 7:18:21 PM6/20/10
to ColdSpring Users Group
Hi folks,

While Mark Mandel is busy working on the next major release of ColdSpring (codename Narhwal), the most of the rest of us are still using ColdSpring 1.2.

Prior to Narhwal ColdSpring used CVS for it's official source code repository, which is a bit hard to work with. I had made fixes and tweaks to my own ColdSpring install but have only managed to get one patch accepted into the CVS repository. I imagine that CVS is as difficult to work with for owners as it is for contributors, so I don't really blame anyone for the slow process for reviewing and accepting patches.

I have recently started getting into Git, so as a way to share my patches with others I have imported the official CVS repository into a local Git repository and pushed it back out to GitHub. You can find the GitHub repository at http://github.com/boomfish/coldspring1.

A few notes:
  1. Because I used git-cvsimport, the GitHub repository includes a history of the commits performed on the CVS repository. This makes for a better starting point than the more common process of using the contents of a zip file for an initial import.
  2. I also pushed the CVS tag 'coldspring-1-2' (corresponding to the last official release) to GitHub, so use that Git tag if you want the source that corresponds to the official zip file.
  3. The 'master' branch corresponds to the imported CVS repository. I have been applying my own patches to a 'boomfish' branch in order to keep master pristine.
If you have your own patches for ColdSpring 1.2 that you would like to share, I encourage you to fork my repository on GitHub.

Cheers,

-- Dennis
Reply all
Reply to author
Forward
0 new messages