Lines Matching +full:push +full:- +full:pull
3 Creating Pull Requests
6 This chapter describes how maintainers can create and submit pull requests
11 experienced maintainer) primarily from comments made by Greg Kroah-Hartman
22 -------------
25 the pull request on a separate branch. Typically you will base this branch
26 off of a branch in the developers tree whom you intend to send the pull
29 In order to create the pull request you must first tag the branch that you
35 Greg offers the following. A pull request with miscellaneous stuff for
36 drivers/char, to be applied at the Kernel version 4.15-rc1 could be named
37 as ``char-misc-4.15-rc1``. If such tag would be produced from a branch
38 named ``char-misc-next``, you would be using the following command::
40 git tag -s char-misc-4.15-rc1 char-misc-next
42 that will create a signed tag called ``char-misc-4.15-rc1`` based on the
43 last commit in the ``char-misc-next`` branch, and sign it with your gpg key
44 (see :ref:`Documentation/maintainer/configure-git.rst <configuregit>`).
46 Linus will only accept pull requests based on a signed tag. Other
50 you to describe the tag. In this case, you are describing a pull request,
54 merge the pull request. So write it up well, as it will be in the kernel
60 to understand what I'm pulling, and why I should pull it. I also
65 Note that if there is something odd about the pull request, that
70 (or even bug-fixes, but ones that look scary), explain not just
74 I will take both what you write in the email pull request _and_ in
77 make it into the pull request email), or you can make the signed
79 the work later when you actually send me the pull request.
83 partly because part of the message may make sense for me at pull
88 particularly for non-native speakers (but also for native ones
93 Greg gives, as an example pull request::
95 Char/Misc patches for 4.15-rc1
97 Here is the big char/misc patch set for the 4.15-rc1 merge window.
101 - time_travel_controller: Finally a set of drivers for the
105 - relativity_shifters: due to the affect that the
115 linux-next releases, and the original problems that it found have
118 linux-next tree creations.)
120 Signed-off-by: Your-name-here <your_email@domain>
124 for a "summary subject" and be sure to sign-off at the bottom.
126 Now that you have a local signed tag, you need to push it up to where it
129 git push origin char-misc-4.15-rc1
132 Create Pull Request
133 -------------------
135 The last thing to do is create the pull request message. ``git`` handily
136 will do this for you with the ``git request-pull`` command, but it needs a
137 bit of help determining what you want to pull, and on what to base the pull
139 following command(s) will generate a pull request::
141 …git request-pull master git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/char-misc.git/ char-m…
146 'char-misc-4.15-rc1' tag location, to the head of the 'master'
148 tree that I diverged from, usually a -rc release) and to use the
149 git:// protocol to pull from. If you wish to use https://, that
153 If the char-misc-4.15-rc1 tag is not present in the repo that I am
155 a handy way to remember to actually push it to a public location.
157 The output of 'git request-pull' will contain the location of the
158 git tree and specific tag to pull from, and the full text
161 pull request, and a shortlog of the individual commits that the
162 pull request will provide.
166 creating pull requests without a signed tag then ``https://`` may be a
170 Submit Pull Request
171 -------------------
173 A pull request is submitted in the same way as an ordinary patch. Send as
174 inline email to the maintainer and CC LKML and any sub-system specific
175 lists if required. Pull requests to Linus typically have a subject line
178 [GIT PULL] <subsystem> changes for v4.15-rc1