Lines Matching +full:pulled +full:- +full:up
9 experienced maintainer) primarily from comments made by Greg Kroah-Hartman
20 -------------
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).
50 any, testing has been done. All of this information will end up in the tag
52 merge the pull request. So write it up well, as it will be in the kernel
68 (or even bug-fixes, but ones that look scary), explain not just
86 particularly for non-native speakers (but also for native ones
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
131 -------------------
134 will do this for you with the ``git request-pull`` command, but it needs a
136 against (to show the correct changes to be pulled and the diffstat). The
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
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,
155 The output of 'git request-pull' will contain the location of the
169 -------------------
172 inline email to the maintainer and CC LKML and any sub-system specific
176 [GIT PULL] <subsystem> changes for v4.15-rc1