Work at SourceForge, help us to make it a better place! We have an immediate need for a Support Technician in our San Francisco or Denver office.
which is the best way to send a patch?
Perferrably use the SourceForge patch tracker at <http://sourceforge.net/tracker/?atid=635945&group_id=103788&func=browse>.
The repository is recently converted from CVS to SVN, I have to update this in the the developer guide. The past few days of development have taken place in the SNV repository, the CVS repository already is a bit out of date (mostly cleanups though). For details on the SVN repository, see <http://sourceforge.net/svn/?group_id=103788>.
Either use "svn diff >patch.txt" to create a patch, or zip the changed source files into an archive.
The developer guide has been updated, and describes how to connect to the SVN repository. For more information, refer to <http://jomic.sourceforge.net/developer-guide.html>.