If you have some changes you'd like to see added to a future release, here are some guidelines for submitting patches. Don't worry - we're not very anal about people following these procedures, but they do make the patches easier for us to consume.
Patches should be in unified diff form. If your changes are localized to one file, you can create a patch using a command like:
diff -u getimage.orig getimage
If your changes are in multiple files, you can create a patch using a command like:
diff -urN systemimager.orig/ systemimager/
Review your patches to make sure that you aren't changing other things. Even if the additional changes are just whitespace changes, they can make the patch more difficult to review and reduce the chances it can cleanly apply against a slightly different tree.
Its easiest if patches are against the code in an up-to-date tree of the code branch you're changing. For example, if you've fixed a bug in 3.0.0, check out the v3_0_x branch and create your diff against that tree. This will prevent you from fixing a bug that has already been fixed and committed, or creating a patch against a version that is different enough that it won't apply cleanly to the current code.
For patches that are in SystemImager code, and do not affect other components of the System Installation Suite, please submit to systemimager-devel@lists.sourceforge.net. For patches that you think mayb relevant to the rest of the System Installation Suite, use sisuite-devel@lists.sourceforge.net. If you're not sure which one to use, use the latter.