Contribute/SubmitAPatch: Difference between revisions

From QEMU
No edit summary
mNo edit summary
Line 16: Line 16:


For smaller patches in less frequently changed areas of QEMU, consider using the [[Contribute/TrivialPatches|trivial patches]] process.
For smaller patches in less frequently changed areas of QEMU, consider using the [[Contribute/TrivialPatches|trivial patches]] process.
[http://www.celebswear.com leather Jacket]
[http://www.celebswear.com leather Jackets]
[http://www.celebswear.com Cheap leather Jacket]
[http://www.celebswear.com Men leather Jacket]
[http://www.celebswear.com Mens leather Jacket]
[http://www.angeljackets.com leather jackets]
[http://www.angeljackets.com black leather jackets]
[http://www.angeljackets.com leather blazer]
[http://www.angeljackets.com bomber leather jacket]
[http://www.angeljackets.com discount leather jackets]
[http://www.angeljackets.com lambskin leather jacket]

Revision as of 09:30, 15 August 2011

All contributions to QEMU are sent as patches to the qemu-devel mailing list. Patch contributions should not be posted on the bug tracker, posted on forums, or externally hosted and linked to.

You get a better chance to get a reply if you follow the LKML rule of send directly to the maintainer of the portion of the patch (see MAINTAINERS file). Also keep attention to reply to all and not just the sender.

Consider also to prefix your patch commit messages with the portion you changed (ie: block or tcg).

Send patches inline so they are easy to reply to with review comments. Do not put patches in attachments.

Patch emails must include a Signed-off-by: line. For more information see SubmittingPatches 1.12.

Follow the coding style and run scripts/checkpatch.pl <patchfile> before submitting. See also:

Split up longer patches into a patch series of logical code changes. Each change should compile and execute successfully.

For smaller patches in less frequently changed areas of QEMU, consider using the trivial patches process.