CVS is down because of the attack on SourceForge. I'll probably give it to the end of week or so to see if it comes back up. Either way, I'll be moving source control to SVN. The question is whether the existing history will go with it. At that point, I'll apply the patches that make sense for the goals of the code, check in some bug fixes, and push a new version.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Months later…good news, CVS is back up. Bad news, haven't switched to SVN. I think it's better to spend what little time I have on this fixing a few bugs and releasing a new version. Moving to SVN/git will stay on the "todo" list.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
CVS is down because of the attack on SourceForge. I'll probably give it to the end of week or so to see if it comes back up. Either way, I'll be moving source control to SVN. The question is whether the existing history will go with it. At that point, I'll apply the patches that make sense for the goals of the code, check in some bug fixes, and push a new version.
Months later…good news, CVS is back up. Bad news, haven't switched to SVN. I think it's better to spend what little time I have on this fixing a few bugs and releasing a new version. Moving to SVN/git will stay on the "todo" list.
If you could eventually use git, that would be wonderful.
Meanwhile, thank you for the recent bug fixes and the new point release.
Blessings!
Augustin.