Lines Matching +full:pulled +full:- +full:up

11 experienced maintainer) primarily from comments made by Greg Kroah-Hartman
22 -------------
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>`).
52 any, testing has been done.  All of this information will end up in the tag
54 merge the pull request. So write it up well, as it will be in the kernel
70 	(or even bug-fixes, but ones that look scary), explain not just
88 	particularly for non-native speakers (but also for native ones
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
133 -------------------
136 will do this for you with the ``git request-pull`` command, but it needs a
138 against (to show the correct changes to be pulled and the diffstat). The
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
153 	If the char-misc-4.15-rc1 tag is not present in the repo that I am
154 	asking to be pulled from, git will complain saying it is not there,
157 	The output of 'git request-pull' will contain the location of the
171 -------------------
174 inline email to the maintainer and CC LKML and any sub-system specific
178 	[GIT PULL] <subsystem> changes for v4.15-rc1