Lines Matching +full:use +full:- +full:push +full:- +full:pull
1 Creating Pull Requests
4 This chapter describes how maintainers can create and submit pull requests
9 experienced maintainer) primarily from comments made by Greg Kroah-Hartman
20 -------------
23 the pull request on a separate branch. Typically you will base this branch
24 off of a branch in the developers tree whom you intend to send the pull
27 In order to create the pull request you must first tag the branch that you
33 Greg offers the following. A pull request with miscellaneous stuff for
34 drivers/char, to be applied at the Kernel version 4.15-rc1 could be named
35 as ``char-misc-4.15-rc1``. If such tag would be produced from a branch
36 named ``char-misc-next``, you would be using the following command::
38 git tag -s char-misc-4.15-rc1 char-misc-next
40 that will create a signed tag called ``char-misc-4.15-rc1`` based on the
41 last commit in the ``char-misc-next`` branch, and sign it with your gpg key
42 (see Documentation/maintainer/configure-git.rst).
44 Linus will only accept pull requests based on a signed tag. Other
48 you to describe the tag. In this case, you are describing a pull request,
52 merge the pull request. So write it up well, as it will be in the kernel
58 to understand what I'm pulling, and why I should pull it. I also
59 want to use that message as the message for the merge, so it should
63 Note that if there is something odd about the pull request, that
68 (or even bug-fixes, but ones that look scary), explain not just
72 I will take both what you write in the email pull request _and_ in
75 make it into the pull request email), or you can make the signed
77 the work later when you actually send me the pull request.
81 partly because part of the message may make sense for me at pull
86 particularly for non-native speakers (but also for native ones
91 Greg gives, as an example pull request::
93 Char/Misc patches for 4.15-rc1
95 Here is the big char/misc patch set for the 4.15-rc1 merge window.
99 - time_travel_controller: Finally a set of drivers for the
103 - relativity_shifters: due to the affect that the
113 linux-next releases, and the original problems that it found have
116 linux-next tree creations.)
118 Signed-off-by: Your-name-here <your_email@domain>
122 for a "summary subject" and be sure to sign-off at the bottom.
124 Now that you have a local signed tag, you need to push it up to where it
127 git push origin char-misc-4.15-rc1
130 Create Pull Request
131 -------------------
133 The last thing to do is create the pull request message. ``git`` handily
134 will do this for you with the ``git request-pull`` command, but it needs a
135 bit of help determining what you want to pull, and on what to base the pull
137 following command(s) will generate a pull request::
139 …git request-pull master git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/char-misc.git/ char-m…
144 'char-misc-4.15-rc1' tag location, to the head of the 'master'
146 tree that I diverged from, usually a -rc release) and to use the
147 git:// protocol to pull from. If you wish to use https://, that
151 If the char-misc-4.15-rc1 tag is not present in the repo that I am
153 a handy way to remember to actually push it to a public location.
155 The output of 'git request-pull' will contain the location of the
156 git tree and specific tag to pull from, and the full text
159 pull request, and a shortlog of the individual commits that the
160 pull request will provide.
164 creating pull requests without a signed tag then ``https://`` may be a
168 Submit Pull Request
169 -------------------
171 A pull request is submitted in the same way as an ordinary patch. Send as
172 inline email to the maintainer and CC LKML and any sub-system specific
173 lists if required. Pull requests to Linus typically have a subject line
176 [GIT PULL] <subsystem> changes for v4.15-rc1