Lines Matching full:misc

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