How To Submit Patches

Quick run-down of things that will make it more likely that your patch is accepted (outside of the Tomboy/CodingGuidelines):

Create a patch file

Don't try to solve multiple problems in one patch -- not only will it make us reject the whole patch if one of the problems is poorly solved, it also makes it harder for us to evaluate what is solved by a particular change.
In particular, don't try to clean up indentation, comments or the like. This will just make it harder for us to read. If you want to clean stuff up, do it in a separate patch.
Create your patch
- Commit your work to your local git repo using git commit
- Create a patch in the proper format, with author and commit message using git format-patch HEAD^ (This will generate a file from the commit 0001-your-commit-title.patch)
- Others should be able to apply your patch by running git am 0001-your-commit-title.patch.
- Please see Git/Developers for more information on using git to contribute to GNOME projects.
Make sure you base your patch off of the latest version in Git (by typing git pull --rebase after committing), if possible.

Always look at your patch file in its entirety before submitting it. Make sure it doesn't include any non-related files (such as *.po translation files).
Post the patch as an attachment to the appropriate bug report in bugzilla. This will ensure that vital spaces are retained.
Your patch is less likely to be forgotten if put in a bug report rather than submitted through the Tomboy mailing list, as those can be efficiently searched for.
Describing roughly how you solve the problem will make it easier to evaluate the patch.
If your patch includes a UI change, please include a screen shot of the resulting UI and include in the bug report.

(original text for this page taken from Dia/HowToSubmitPatches)