Lines Matching full:to

6 QEMU welcomes contributions of code, but we generally expect these to be
7 sent as simple patch emails to the mailing list (see our page on
10 will need to submit pull requests, although occasionally for a large
11 patch series we might ask a submitter to send a pull request. This page
14 A good rule of thumb is not to send a pull request unless somebody asks
15 you to.
18 threaded as follow-ups to the pull request itself. The simplest way to
19 do this is to use ``git format-patch --cover-letter`` to create the
20 emails, and then edit the cover letter to include the pull request
26 helps people to filter in or out the resulting emails (especially useful
34 **Don't forget to add Reviewed-by: and Acked-by: lines**. When other
37 tool <https://github.com/stefanha/patches>`__ to add patches from email
38 directly to your git repo it will include the tags automatically; if
39 you're updating patches manually or in some other way you'll need to
43 request says these patches are ready to go into QEMU now, so they must
45 corrected issues in one round of code review, you need to send your
46 fixed patch series as normal to the list; you can't put it in a pull
47 request until it's gone through. (Extremely trivial fixes may be OK to
50 **Test before sending**. This is an obvious thing to say, but make sure
66 "PULL". This allows it to be automatically filtered out of the set of
67 pull requests that should be applied to master.
72 sanity checks. Note that you must edit it to configure it suitably for