From Annvix
Developer's Reference: Building Annvix: FAQ
Submitting and formatting patches
Patches to code and spec files should follow the following guidelines:
- Patches must be in diff -uN format
- Patches must be atomic
- Base patches must be based on the current development branch (currently CURRENT_1_1)
- Patches should be sent to the dev@ mailing list for approval and review and they should be sent as attachments (not inline!). This means that those using Mozilla or Thunderbird as their email client should set user_pref("mail.content_disposition_type", 1); in your prefs.js file (otherwise they will always be sent inline)
Alignment and spacing in code and specs
We're a little particular about formatting for Annvix and this has to do with code and spec readability. If anyone has looked at Mandriva or Fedora spec files and compared them to SUSE specs, you'll know what we mean. A hard to read spec can be very difficult to work with.
For that reason, and for "portability" amongst editors, we prefer that indentation be done with four spaces rather than tabs. Even if you set your tab stop to four spaces in your preferred editor, this may not carry over to all editors, so please use spaces. Even for eight character indentation (the typical amount of characters for a tab), please use spaces.
Furthermore, functions should be indented appropriately (if statements, for loops, etc.) and statements inside a pushd/popd pair should also be indented. If you have any doubts, look at existing code and spec files to see how we are doing it.
