Following are suggested guidelines for submitting packages for a future release that make it easier to incorporate the changes.
Patches should be in unified diff form. If your changes are localized to one file, you can create a patch using a command such as:
diff -u getimage.orig getimage
If your changes are in multiple files, you can create a patch using a command such as:
diff -urN systemimager.orig/ systemimager/
Review your patches to make sure 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.
It's 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 to prevent you from fixing a bug that has already been fixed and committed or from creating a patch against a version that is different enough that it won't apply cleanly to the current code.
Please submit patches to SystemImager code that do not affect other components of the System Installation suite to systemimager-devel@lists.sourceforge.net. For patches relevant to the rest of the System Installation Suite, submit to sisuite-devel@lists.sourceforge.net. Use the latter if unsure which one to use.