Chapter 4. Coding Practice

Table of Contents
4.1. Patch Format
4.2. Some notes about style
4.3. Quality Assurance
4.4. Porting Wine to new Platforms
4.5. Adding New Languages

This chapter describes the relevant coding practices in Wine, that you should be aware of before doing any serious development in Wine.

4.1. Patch Format

Patches are submitted via email to the Wine patches mailing list, . Your patch should include:

To generate a patch using Git, first commit it to your local tree.

Each file that you change needs to be updated with git update . If you are adding or removing a file, use git update --add or git update --remove respectively. After updating the index, commit the change using git commit . The commit message will be sent with your patch, and recored in the ChangeLog.

After committing the patch, you can extract it using git format-patch and send it to wine-patches using git imap-send or simply attaching it to you mail manually.