docs/devel/submitting-a-pull-request.rst

1 .. _submitting-a-pull-request:
7 sent as simple patch emails to the mailing list (see our page on
8 :ref:`submitting-a-patch`
11 patch series we might ask a submitter to send a pull request. This page
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.
24 retransmitted patch mails (for example, by using
25 ``--subject-prefix=PULL`` in your ``git format-patch`` command). This
29 **Each patch must have your own Signed-off-by: line** as well as that of
30 the original author if the patch was not written by you. This is because
31 with a pull request you're now indicating that the patch has passed via
34 **Don't forget to add Reviewed-by: and Acked-by: lines**. When other
46 fixed patch series as normal to the list; you can't put it in a pull
51 everything builds (including that it compiles at each step of the patch
52 series) and that "make check" passes before sending out the pull
54 against bad code, so double check the details.
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>`__