Lines Matching +full:one +full:- +full:way

1 .. _submitting-a-pull-request:
8 :ref:`submitting-a-patch`
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
21 details that ``git request-pull`` outputs.
25 ``--subject-prefix=PULL`` in your ``git format-patch`` command). This
27 if they are only CC'd on one email out of the set).
29 **Each patch must have your own Signed-off-by: line** as well as that of
34 **Don't forget to add Reviewed-by: and Acked-by: lines**. When other
39 you're updating patches manually or in some other way you'll need to
45 corrected issues in one round of code review, you need to send your
53 request. As a submaintainer you're one of QEMU's lines of defense
57 the pullreq email should quote a tag which is a GPG-signed tag (as
58 created with 'gpg tag -s ...'). See :ref:`maintainer_keys` for
69 You might be interested in the `make-pullreq
70 <https://git.linaro.org/people/peter.maydell/misc-scripts.git/tree/make-pullreq>`__