Lines Matching full:misc
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
95 Char/Misc patches for 4.15-rc1
97 Here is the big char/misc patch set for the 4.15-rc1 merge window.
129 git push origin char-misc-4.15-rc1
141 …-pull master git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/char-misc.git/ char-misc-4.15-rc1
146 'char-misc-4.15-rc1' tag location, to the head of the 'master'
153 If the char-misc-4.15-rc1 tag is not present in the repo that I am