Lines Matching +refs:is +refs:direct +refs:push

5 to other maintainers. This is useful for transferring changes from one
12 please direct abuse to Tobin C. Harding <me@tobin.cc>.
28 have just created. It is recommended that you choose a meaningful tag name,
30 practice is to include in the name an indicator of the subsystem of origin
49 so outline what is contained here, why it should be merged, and what, if
57 	Anyway, at least to me, the important part is the *message*. I want
63 	Note that if there is something odd about the pull request, that
95 	Here is the big char/misc patch set for the 4.15-rc1 merge window.
96 	Contained in here is the normal set of new functions added to all
109 		  There is a Kconfig option to force these to be enabled
121 The tag message format is just like a git commit id.  One line at the top
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
133 The last thing to do is create the pull request message.  ``git`` handily
143 	This is asking git to compare the difference from the
151 	If the char-misc-4.15-rc1 tag is not present in the repo that I am
152 	asking to be pulled from, git will complain saying it is not there,
153 	a handy way to remember to actually push it to a public location.
157 	description of that tag (which is why you need to provide good
171 A pull request is submitted in the same way as an ordinary patch. Send as